Deploy via "Publish to Update Set..." after deploying via Application Repository?

[Joseph Warner]

Will it cause problems if I deploy a scoped application using Publish to Update Set... after I have already deployed using the Application Repository (Azure git)?

I have taken over a scoped application from the previous developer. The application was deployed using update sets (about 100 update sets) and was then linked to an Azure repository with the Yes, do retain update set history as commits option selected. Subsequently, roughly 150 commits were deployed from the Application repository (Azure).

Will it cause issues if I revert to deploying using the My Company Applications > Publish to Update Set, despite having previously deployed from the Application Repository?

My concern is that there is no longer any traceability when deploying via the Application Repository, whereas with update sets you can see what files changed.

 

[Allen Andreas · Accepted solution]

Hi,

Is the app installed on the sys_store_app due to being pushed via the app repo?

If you use update sets, it's instead on the sys_app table and could be considered a different install.

More info to consider here: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715422 

[Joseph Warner]

Yes, this is the article I was looking for. Thank you!