Can you use both Update Set and Source Control at the same time to track your development changes?

[Johannes Mweli]

Hi ServiceNow Community Developers,

I am working on a requirement where I am doing a POC to see if we can use GitHub as a source control tool to track our development changes. Based on the investigation that I have done so far it looks like one cannot use both Update Sets and Source Control at the same time to track the customizations. In other words if I use Source control I can't use Update sets and vice versa. Is this assumption true. Do you guys know if both the Update Set and the Source Control can be used at the same time or not? Please advise.

Thanks,

Johannes 

[Bert_c1]

Seems a good discussion on this is here:

https://www.servicenow.com/community/developer-forum/will-github-replace-update-sets/m-p/1605636

I prefer using the App Repository to move app versions between instances. Seems use of GitHub on dev may be useful, for any changes that are not captured in sys_update_version table. For changes that are captured there, using that version history or GitHub is the same.

I suspect others here will post their opinions.

I think your main concern may be how to preserve any development work, that hasn't been promoted to higher instances, when the dev instance is cloned over.  Any update sets in progress or have not been promoted need to be exported (in-progress update set set to complete and exported) so they can be restored after a clone. Using GitHub may be easier, as those updates a stored in an accessible place.  Publishing new app versions to the App Repository primarily changes how new work is deployed to higher instances.