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

[cloudyrobert]

Interesting--thank you, sir!