---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Explore

# Exploring ReleaseOps {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 min. de leitura

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 {#exploring-release-ops__cf-exploring-parent-overview}

ReleaseOps automates the 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 users {#exploring-release-ops__cf-exploring-parent-users}

{#exploring-release-ops__table_o3d_jq4_zfc__entry__2}

| Role | Description |
|-|-|
| Pipeline manager | A pipeline manager is responsible for creating and managing pipelines, including customizing playbooks. Pipelines define the flow of your deployments. |
| Release manager | A release manager is responsible for creating and scheduling releases, as well as verifying that the contents of a release are both relevant and correct. The release manager can remove deployment request items that don't meet the criteria for the release. |
| Developer | A developer is responsible for creating deployment requests to push application installations or update sets of work through the pipeline. |
| Tester | A tester is responsible for signing off on ATF test failures that occur to enable a deployment to continue. A tester can also send it back to development. |
[Tabela 1. Users]

{#exploring-release-ops__table_o3d_jq4_zfc}

## ReleaseOps workflow {#exploring-release-ops__cf-exploring-parent-workflow}

The following workflow illustrates the sample pipeline workflow installed with ReleaseOps. Your pipeline manager can customize it as needed.
Figura 1. ReleaseOps sample pipeline workflow

In the traditional development to test to production workflow:

1. A release manager creates a release, which is associated with a pipeline.
2. Developers make changes through update sets. Once they mark an update set Complete and promote the update set for deployment, the update set is added to an existing deployment request or to a new deployment request, which is targeted to a release.
3. Developers add runbook tasks to deployment requests to enable custom and manual activities to occur throughout the assessment and release playbook stages.
4. When the update sets within a deployment request are functional and ready to be deployed, a developer sets the deployment request state to the Ready to assess.
5. The assessment playbook runs, during which Automated Test Framework (ATF) test suites and instance scans are run on the changes in the deployment request.
6. If there are failures during assessment, deployment tasks are created that the tester can sign off on or redirect to the developer to address.
7. If there are any runbook tasks set to occur during the assessment playbook stage, progression pauses until the runbook tasks have been addressed.
8. Once the deployment and runbook tasks have been addressed, the deployment request state is set to Ready for deployment.
9. On the scheduled date for the release, the release playbook runs.
10. If there are any runbook tasks set to occur during the release playbook stage, progression pauses until the runbook tasks have been addressed.
11. Once the runbook tasks have been addressed, all deployment requests in the Ready for deployment state move through the pipeline to production.

{#exploring-release-ops__ol_rg1_3hl_1gc} Figura 2. ReleaseOps sample release workflow

In the traditional release workflow:

1. A release manager creates a release and sets the state to Active.
2. On the scheduled freeze date, the release begins preparing for deployment.
3. During the preparation process, deployment requests that aren't ready are set to Deferred and can be attached to a future release.
4. Once preparation is complete, the release state is set to Ready for deployment.
5. When the release date arrives, the update sets within the deployment requests move from test to production in the order that they were deployed in the last instance.
6. The release and deployment requests are set to Complete.
{#exploring-release-ops__ol_i1r_mbg_cgc}

## ReleaseOps benefits {#exploring-release-ops__cf-exploring-parent-benefits}

{#exploring-release-ops__table_r3d_jq4_zfc__entry__3}

| Benefit | Feature | Role |
|-|-|-|
| Define requirements for an application or update to get installed on a target instance. | [Pipelines in ReleaseOps](https://servicenow-prod.fluidtopics.net/42KOEoNHgJnf7PKZyD_Z0A "A pipeline is the flow of a deployment in ReleaseOps. A pipeline's flow is defined within playbooks, which enables you to customize as needed.") | Pipeline Manager |
| Deploy changes to a production or another target environment. | [Releases in ReleaseOps](https://servicenow-prod.fluidtopics.net/G~aRMdRk50bi08BCIgmv7w "Scheduled and on-demand releases are how changes are deployed to target instances with ReleaseOps. Releases can contain one or more deployment requests.") | Release Manager |
| Push application installations or update sets of work completed through the pipeline with deployment requests. | [Deployment requests in ReleaseOps](https://servicenow-prod.fluidtopics.net/l5gfyUiQU9luqmrYMuvAbw "Deployment requests contain one or more update sets, and are contained in a release.") | Developer |
| Scan deployment requests for changes to the current state of the production instance or target instance with the deployment analyzer. Use those findings to determine your actions in the pipeline. | [Deployment analyzer in ReleaseOps](https://servicenow-prod.fluidtopics.net/3CwzGTwmbt0UhRgjciteMQ "The deployment analyzer reviews the update set in your release against rules to verify compliance with customizable rules.") | Developer |
| Leverage Automated Test Framework (ATF) code coverage to improve the efficacy of ATF test suites. | [Deployment analyzer in ReleaseOps](https://servicenow-prod.fluidtopics.net/3CwzGTwmbt0UhRgjciteMQ "The deployment analyzer reviews the update set in your release against rules to verify compliance with customizable rules.") | Developer |
| Add custom, flexible, and manual activities to your assessment and release playbooks, without having to adjust the structure of your playbooks each time. | [Runbook tasks in ReleaseOps](https://servicenow-prod.fluidtopics.net/wXWAsLlfdqwesfS0dMeCYA "Learn about how runbook tasks enable flexibility in ReleaseOps deployments, without needing to customize playbooks each time.") | Developer |
[Tabela 2. ReleaseOps benefits]

{#exploring-release-ops__table_r3d_jq4_zfc}

## What to explore next {#exploring-release-ops__cf-exploring-parent-links}

To learn more about configuring and using ReleaseOps, see:

* [Configuring ReleaseOps](https://servicenow-prod.fluidtopics.net/4N61j00zWVG8e3q1Sbi5Zw "Configure ReleaseOps to move changes from development to testing to production.")
* [Using ReleaseOps to manage deployments](https://servicenow-prod.fluidtopics.net/g7AIh5xL38Ey0v~E2XICOA "Use ReleaseOps to automate the process of managing your releases and deploying changes to a target instance.")
* [Promote an update set for deployment](https://servicenow-prod.fluidtopics.net/5eMAXnyQrczyTz9WkSIU1w "When you're ready to deploy your changes, promote your update set to begin the deployment process.")
* [Create a deployment request for a scheduled release](https://servicenow-prod.fluidtopics.net/snoh5QvgpCXlOzBdkCvTTQ "Create a deployment request for a scheduled release to contain your update set and enable your changes to move through the pipeline for deployment.")
* [Create a deployment request for an on-demand release](https://servicenow-prod.fluidtopics.net/z5tbKZrUbMyCwSxR5gAVmw "Create a deployment request for changes that will deployed with an on-demand release.")
* [Attach an update set to an existing deployment request](https://servicenow-prod.fluidtopics.net/36gwojgtMnwa6oFdUr1DPA "If you want to attach multiple update sets to a deployment request, you can attach an update set to an existing deployment request on the Deploy an update set form.")
* [Create a release](https://servicenow-prod.fluidtopics.net/2Gq9N1~SLeTZumtFsch5OQ "Specify the details for your release, including the target instance that the changes will be deployed to and when the release should occur.")
{#exploring-release-ops__ul_s3d_jq4_zfc}