I’m sure many of you have seen this process for building a new Scoped App:
That last step: Manage app deployments using Pipelines and Deployments. Do you use GIT, App Repo, Update Sets, or CICD? If everything went smooth with no defects/incidents, any of them would work, but what if you get a defect/incident?
New with the Zurich release, ServiceNow® ReleaseOps is a solution to the problem of the manual and often error-prone nature of deployment of changes, customizations, and custom apps within the ServiceNow AI Platform.
ReleaseOps overview:
ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production. ReleaseOps pipelines are defined in a playbook, enabling you to customize as needed.
Releases are managed within a release object that contains one or more deployment requests. Each deployment request tracks one or more update sets, which can contain application installs.
Releases are managed from your production instance, where the playbook is executed. Actions are orchestrated across instance with a cross-instance communication layer, alleviating credential setup across instances.
ReleaseOps sounds like a great solution. I haven’t used it yet but do look forward to using it soon. In the meanwhile, I’ll share what has been successful for us. If this is something that works for you, great!
- We primarily use App Repo to promote the code and move it up the stack.
- If we get an Incident, we will use an Update Set.
- At the time of a major release, App Repo will be promoted to Production. Before the move, we execute a fix script that sets the “Replace on upgrade” field to ‘Yes’ for all records within the scope. This ensures that no records are missed or appear in the skipped log awaiting resolution.
I’ll make sure to do a follow-up after I put ReleaseOps through the test!
Thanks for reading!
1 Comment
