Pipelines and Deployments configuration tasks

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Pipelines and Deployments Configuration Tasks

    This document outlines the configuration tasks necessary for setting up Pipelines and Deployments within ServiceNow. Completing these tasks in the specified order is essential for ensuring a successful setup across production and non-production environments.

    Show full answer Show less

    Key Features

    • Environment Credentials: Configure credentials for your instances to allow access via the pipelines.
    • Environment Setup: Establish production and non-production environments by adding URLs and credentials.
    • Pipelines Configuration: Name and configure each pipeline, detailing the associated environments and deployment order.
    • User Management: Add relevant users to the App Engine admin group as necessary.
    • Testing Frameworks: Incorporate Automated Test Framework (ATF) and Instance Scan suites to enhance application deployment.
    • Change Management Integration: Connect existing Change Management programs for automated scheduling of deployments.
    • Controller Instance Setup: Identify the controller instance to manage the deployment flows and data communication.

    Key Outcomes

    By completing the configuration tasks, you can expect:

    • Seamless integration of pipelines with existing environments.
    • Effective management of application deployments through defined workflows.
    • Automation of deployment scheduling aligned with Change Management processes.
    • Enhanced testing capabilities through the use of ATF and Instance Scan suites.

    As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances.

    Setting up environments, pipeline records, and user access

    The tasks for configuring Pipelines and Deployments are listed below, along with links to detailed instructions for completing them. These tasks build on each other, so it's important to complete them in the sequence listed in the Guided Setup.

    Table 1. Pipelines and Deployments configuration tasks
    Instance Task Description
    Production Configure environment credentials. Configure credentials for each instance in your pipeline so that the flows used by AEMC can access the instances in your pipelines.

    For more information, see Configure environment credentials.
    Configure environments. Set up your production and non-production (that is, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance.

    For more information, see Configure your pipeline environments.
    Configure pipelines. Set up and configure each pipeline by naming the pipeline, identifying each of the environments associated with the pipeline, and specifying the order in which apps are deployed between the environments in that pipeline.

    For more information, see Configure your pipeline.
    Add users to the App Engine admin group. Add users involved with this flow of tasks to the App Engine admin group.
    Note:
    If already added users on the production instance using AES guided setup or Configure Application Intake guided setup, you can skip this step.

    For more information, see Add users to the App Engine Admin group.
    Add Automated Test Framework (ATF) and Instance Scan suites.

    Add your customized test suites as part of an application deployment in addition to the instance scan and ATF testing suites that are standard in AEMC.

    For more information, see Add ATF and instance scan suites for testing.
    Enable Change Management integration

    Connect an existing Change Management program with AEMC so that deployments through the pipeline to the production environment are automatically scheduled based on the Change request state and planned change window.

    For more information, see Enable Change Management integration.
    Configure properties to integrate Change Management

    Change requests and configuration items (CIs) are created using specifications set up in your existing Change Management program. If you want to change the change model, change template, or CI creation subflows used during app deployments, you must configure these properties during Guided Setup.

    For more information, see Configure properties to integrate Change Management.
    Testing Configure environment credentials For more information, see Configure environment credentials.
    Configure the controller instance Identify the controller instance that contains the pipeline deployment flows, as well as all of the data associated with the pipeline. As each instance completes its assigned tasks, it communicates with the controller instance to determine where the next stage of deployment takes place.
    Note:
    Your production instance should be identified as the controller.

    For more information, see Configure your controller instance.
    Enable ATF properties on instances of type Testing. Enable system properties that allow the ATF suite to run during the deployment process. If you do not enable these properties, a warning displays during the deployment process, but you can continue with the deployment.
    Note:
    If you plan on cloning your production instance to one or more non-production instances, you should either create a data preserver for these settings or enable these settings on your production instance. For more information, see Create a clone preserver.

    For more information, see Enable Automated Test Framework (ATF) properties.
    Configure Automated Test Framework (ATF) suite For more information, see Exploring Automated Test Framework.
    Configure Instance Scan suite For more information, see Configuring Instance Scan.
    Non-production instances that aren’t of type Testing Configure environment credentials For more information, see Configure environment credentials.
    Configure the controller instance in your non-production instances For more information, see Configure properties to integrate Change Management.