Model an Azure pipeline in DevOps

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 3 minutes to read

    • Model an Azure pipeline by mapping the pipeline to an app, and mapping DevOps Change Velocity pipeline steps to Azure pipeline jobs.

    Before you begin

    Role required: sn_devops.admin

    Procedure

    1. Map your pipeline to an app in DevOps.
      1. Navigate to DevOps > Apps & Pipelines > Apps and open the application record to associate with the pipeline.
      2. In the Pipelines related list, click Edit... to select a pipeline to associate with the app, or click New to create the pipeline.
        Note:
        While associating a pipeline with an app, the pipeline steps are also fetched during import.

        For a new pipeline, fill in the Orchestration pipeline field using the project name and pipeline name as specified in Azure DevOps Pipelines in path format.

        For example, My Project/My Classic Build Pipeline.

        Note:
        The project name must be specified with the pipeline because there could be multiple pipelines with the same name in different projects.
      3. Click Submit.
    2. Open the pipeline record again and select the Track check box so events from the pipeline are received.
      The Track check box must be selected to integrate the pipeline with DevOps Change Velocity.
    3. Create DevOps steps automatically or manually to map to each Azure pipeline job so an orchestration task can be created.
      Note:
      Manual creation of steps is not required when you Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions.
      • Automatically create and map pipeline steps in DevOps by running your Azure pipeline when you Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions.

        Pipeline steps are automatically created, mapped, and associated when DevOps receives step notifications from your Azure pipeline during the run.

      • Manually create and map each pipeline step to an Azure pipeline job.

        In the Steps related list, click New to create a DevOps step for each Azure pipeline job (Orchestration stage field).

        Note:
        The Orchestration stage field value of each step is case-sensitive and must match the original name of the corresponding Azure pipeline job.
        Name

        Name of the pipeline step.
        Pipeline Pipeline in which the step is configured.
        Type Pipeline step type.
        • Build and Test
        • Test
        • Deploy
        • Deploy and Test
        • Manual
        • Prod Deploy
        Order

        Order in which the steps are run.

        Note:
        The step order determines the order of the cards in the Pipeline UI.

        The order of the cards in the Pipeline UI is by task execution.
        Orchestration stage

        Azure pipeline job name (case-sensitive).

        Note:
        For step association with Azure pipeline jobs, the Orchestration stage field must be configured.
        Business service Configuration service that applies to the step.

        Once orchestration tasks are created, associate each orchestration task in the Orchestration Tasks related list with a DevOps pipeline step.

    4. Enable change control automatically or manually.
      • If you are using the ServiceNow DevOps extension for Azure DevOps, run your Azure DevOps pipeline to automatically enable change control.
      • If you are configuring change control manually, select the Change control check box in a step to enable change acceleration and the corresponding configuration fields. For Azure release (CD) pipelines, enable change control in the first step of the required stage only. Change control for Azure release (CD) pipelines is supported only in pre-deployment gates.
        Note:
        ServiceNow Change Management must be installed for change acceleration.
        Change receipt

        Select to enable change receipt for the step so the pipeline doesn't pause when a change request is created.

        All pipeline data is included in the change, but approval is not required for the pipeline to proceed.
        Change approval group

        Approval group for the change request.

        The change approval group becomes the Assignment group in the DevOps change request.

        Note:
        Ensure that the selected group has members and a group manager so the approver field is not empty.
        Change type Change request type to create.
        • Normal (default)
        • Standard
        • Emergency
        Change model Change model for the change request. For more information, see DevOps change models.

        Template

        Note:
        This field is shown only when Change type is Normal or Emergency.

        List of templates to use to auto populate fields for Normal or Emergency change requests.

        Select a template or create a new one.

        Standard change template

        Note:
        This field is shown only when Change type is Standard.
        		 List of standard change templates to use for Standard change requests.
        Note:
        This field is required for Standard change type.
        Change controlled branches

        (Multibranch only) Comma-separated list of branches under change control. Wildcards are supported.

        You can set up change control in your Azure DevOps YAML or Classic Azure pipeline using the Azure Invoke REST API or the ServiceNow DevOps extension for Azure DevOps.

    What to do next

    Configure the Azure pipeline for DevOps