- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2025 08:36 AM
Curious if the SDK has reached a level in which it is an approved method for deploying applications to production.
We are currently working on a DevOps pipeline where the pipeline utilizes the SDK to build and deploy the app from a GitHub repo to migrate code from instance to instance and I was curious what the official stance is for utilizing this methodology to deploy applications to the production instance?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 10:33 AM
hello! the best way to accomplish this is to leverage the App Repo. We encourage you to publish your Fluent application to the App Repo and the installing it in Prod through the application manager. You can learn more about this here: https://www.servicenow.com/docs/bundle/yokohama-application-development/page/build/applications/task...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2025 09:34 AM
@Brady Holliday wrote:Hey @EdwinCoronado, thanks for the reply. The issue with how this works currently is that it forces GitHub to not be the actual source for the code deployment. When you publish an application and it is connected to GitHub it adds a commit for that publish. This has at least 2 issues:
1. We control the production branch by not allowing commits directly to the branch, thus publishing requires a 'staging' branch of some sort. This in turn causes a case where you could technically be able to install a version of an application that is not technically in the 'production' branch which leaves a gap open for a syncing nightmare. (This is the same reason why we do not 'Publish' into the dev branch).
2. The 'Publish' of the app from the instance if not careful may contain code that was not moved up through the correct channels.
Essentially what I am trying to say is when trying to utilize a DevOps mindset of having controlled branches (dev, test, production), it requires additional exceptions that are unique to ServiceNow.
We have found ways to work around these issues by building processes to follow however, with the release of the SDK we were hoping that it would open the door for our DevOps Pipelines to be able to pull down the production branch and then build and deploy that branch into our Production environment more natively than how the currently API deployment features are setup, which is more so the heart of this question.
So just to confirm, you are stating that utilizing the SDK to deploy an application to a Production environment is not supported method and is advised against being used?
This is actually an interesting idea. Why not forego the deployment via app repository and directly deploy the SDK (from git pipeline) to production. Your post is 4 weeks old. What's your deployment strategy right now?
