---
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


---

# Manual setup

# Complete ReleaseOps manual setup {#ariaid-title1}

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

Complete ReleaseOps manual setup to configure a new ReleaseOps ecosystem using the sample pipelines and playbooks.

## Por Que e Quando Desempenhar Esta Tarefa

Starting with version 1.2.1 of ReleaseOps, you can use guided setup for a quicker initial configuration experience. For more information, see [Complete ReleaseOps guided setup](https://servicenow-prod.fluidtopics.net/09YH0p_oL17SF0dc0dbLOQ "Starting with version 1.2.1 of ReleaseOps, guided setup helps to make the initial configuration of ReleaseOps easier. Follow the steps in guided setup to begin using ReleaseOps quickly.").

The manual setup procedure outlined in this task can also be used to complete ReleaseOps initial configuration. Manual setup can be useful in more complex setup scenarios and when making changes to your existing ReleaseOps ecosystem.

## Antes de Iniciar

Role required: admin or sn_releaseops.releaseops_pipeline_admin

Confirm that all instances (production, development, and test) have ReleaseOps installed. Your test instance must also have ATF Test Generator and Cloud Runner installed. For more information, see [Install ReleaseOps](https://servicenow-prod.fluidtopics.net/o0aeTK_yvBlWMqv5~2~WPA "Install ReleaseOps from the ServiceNow Store for the first time.").

Confirm that multi-instance management has been configured to enable all non-production instances (development and test) to be managed by the production instance. For more information, see [Configure multi-instance management for instances using ReleaseOps](https://servicenow-prod.fluidtopics.net/ZnoZS2z~p9EQTPN8wAYibw "Manage the multi-instance configurations to enable access across instances in your ReleaseOps ecosystem.").

## Procedimento

1. On your production instance, create a deployment instance record for each instance that you want to participate in your ReleaseOps ecosystem.  
   Nota:  
   For the ReleaseOps sample release pipelines, the three instances are:
   * Development
   * Test
   * Production
   {#configure-new-releaseops-ecosystem__ul_jgd_x3m_dgc}
   1. Navigate to AllReleaseOpsDeployment Instances.
   2. Add a new record for each instance that participates in your ReleaseOps ecosystem by selecting New.
   3. Select the Instance field, then select the instance that you want to add to your ReleaseOps ecosystem.
   4. Select the Instance type field, then select the correct instance type from the list.
   5. Select Submit.
   6. Repeat steps b-e for each instance that participates in your ReleaseOps ecosystem.
   {#configure-new-releaseops-ecosystem__substeps_p2w_dy2_bgc}
2. On your production instance, configure the test instance for both the sample On Demand Pipeline and sample Release Pipeline.  
   For sample ReleaseOps pipelines, you must only configure a new pipeline instance for your test instance. You don't need to configure pipeline instances for your development and production instances, because these environments are defined within deployment requests and releases.

   For custom ReleaseOps pipelines, you can configure additional pipeline instances for the non-production instances that participate in your ReleaseOps ecosystem, excluding your development instance. For more information about custom pipelines, see [Create a custom pipeline](https://servicenow-prod.fluidtopics.net/8t~bU~PpFnt8Xol_H3ibvw#create-release-ops-pipeline "Create a custom pipeline to move changes from your development environment to production (or your target instance) by duplicating one of the ReleaseOps sample playbooks.").
   1. Navigate to AllReleaseOpsPipelines.
   2. Select one of the sample pipeline records from the list.
   3. On the pipeline record, select the Pipeline instances tab in the Related Links section.  
   4. On the Pipeline instances tab, select New.
   5. On the new pipeline instance form, select the Lookup using list icon (![]()) for the Deployment instance field, then select the test instance from the list.
   6. In the Label field, select Test.
   7. Select Submit.
   8. Repeat the process in steps b-g to configure test instances for each of your sample pipelines.
3. On your production instance, navigate to AllSystem Update SetsUpdate Sources and verify that there are valid update sources defined for both your development and test instances.  
   Nota:  
   If there aren't valid update sources defined for both your development and test instances, you can define them by navigating to AllSystem Update SetsUpdate Sources on your development and test instances and creating a new update source record.
4. On your test instance, navigate to AllSystem Update SetsUpdate Sources and confirm that there's a valid update source defined for your development instance.
5. On your development instance, set the property sn_releaseops.deployment_controller to the production (or deployment controller) URL.
   1. Navigate to AllSystem PropertiesAll.
   2. Using the search bar, enter <kbd class="ph userinput"><span class="keyword parmname">sn_releaseops.deployment_controller</span></kbd>.  
   3. Select the record for sn_releaseops.deployment_controller.
   4. In the Value field, enter the URL for your production (or deployment controller) instance.
   5. Select Update.
   {#configure-new-releaseops-ecosystem__substeps_gxj_bd5_dgc}

## Resultado

ReleaseOps is ready to deploy changes from your development to test to production instances.