Scheduled Jobs and other "non-update set" files in a GIT Repo'd App

[kclark1]

Hey Team,

Ran into an interesting challenge with a Source Controlled App that we've built.   It has a couple of Scheduled Job records that need a script change.   We've got the first iteration of the Scheduled Jobs included in the source which is being managed in GITLAB, but because Scheduled Jobs aren't captured by Update Sets, the changes to the scheduled Job file don't get recognised for Commit.

I've tried modifying two files (the Scheduled Job and a random change to a UI Macro file) and tested committing.   it didn't show the scheduled Job file as part of the commit in the popup window, but when I pulled that code to another instance, BOTH updates (the Scheduled Job as well as the UI Macro) were updated.

Worth knowing that Source Control pretends to follow the conventions of Update Sets, but I *think* that it basically does a snapshot of the whole app - probably similar to the App Publish function between instances?

Anyone from ServiceNow able to shed some light here?   ctomasi?   You've done a lot in this space.   Any thoughts?

Cheers,

Kevin

[Chuck Tomasi]

Hi Kevin,

I'm going to have to check in to this. It almost feels like something changed in Studio. I know I have written and maintained scheduled jobs before and they show up under the Server Development section and I can push them to the Git repo, but when I tried it on my personal developer instance today, Commit doesn't even light up on the menu when the scheduled job is the only change.

Let me do some checking and I'll let you know what I find.

[kclark1]

Thanks Chuck.   I'd be interested to see what you learn.   The Scheduled Jobs still commit and pull ok, it's just that as you say, they won't activate the Commit function, nor do they appear in the list of changed files when you apply remote changes (if you've changed a non-scheduled job).   I haven't tested to see if they will stash ok either.

[Robert Elliott1]

Hey @Chuck Tomasi -- did you find an answer on this one?

[Chuck Tomasi]

This might be helpful. There's a new feature in Rome called Selective Commits that may be what you're looking for:

Creator Toolbox: What's new with Source Control in Rome?

Check out "include_untracked" and "exclude_untracked" here too.

Docs: Commit Changes (Rome)