We're currently transitioning to the new ServiceNow IDE/SDK for app development and have hit a roadblock regarding promotion and deployment workflows.
Our setup uses GitHub for source control and CloudBees (Jenkins) for CI/CD to manage code movement across branches. Previously, we leveraged ServiceNow APIs to deploy applications (via Apply Remote Updates) to non-prod environments and then published from our Quality environment post-UAT, making the app available in the store for production installs (and thus ensuring the application isn't available to be installed into production until after UAT is complete, while also automating the install of that version into production).
For our new development life cycle we took the approach of having CloudBees spun up with the SDK installed and then performing the build and deploy commands to deploy to lower environments. However, we’re encountering issues with SDK authentication—it prompts for credentials interactively, which complicates automation and prevents us from executing these commands in a single-line.
Has anyone else faced similar limitations with the new SDK, particularly around promotion and deployment and needing to continue relying on legacy methods of the source control integration?
Additionally, has anyone successfully implemented a fully automated build and deploy pipeline using CloudBees and the ServiceNow SDK—especially for non-prod environments—while still using store-based deployment for production?
Thanks in advance!
