Sign in

Use Case two: Fast release delivery (UAT → PROD)

3 min read

This section describes the fast release delivery scenario for the Release Innovator pipeline, used when a customization must be promoted to UAT and PROD with minimal delay skipping Deploy SIT and Update STG stages while preserving approval controls and release traceability.

The pipeline enables consistent delivery by using build tags to identify and deploy the same release through different stages, from validation environments to production.

Define the Release Name

Define a unique release identifier used to track the deployment across all environments and distinguish it from other releases. Use any meaningful name (for example, a sprint identifier). This value is used as the “Release name” parameter in the Release Innovator pipeline.

Identify the initial CI pipeline Build Number

Determine the initial CI build to be used for UAT update.

This CI pipeline Build is the source of customizations for UAT deployment during release initiation.

CI build for PROD is handled separately and require manual tagging.

Trigger the Pipeline

The following steps outline the process of running the Release Innovator pipeline for a fast release delivery:

  1. Navigate to the Release Innovator pipeline.
  2. Select Run Pipeline.
  3. Select the appropriate Branch/Tag.

  1. Set Release name defined previously.
  2. Select the Skip “Deploy SIT” stage option to begin the process from UAT.

  3. To tag identified initial CI pipeline for UAT check “Put tags on selected CI build for SIT and UAT environments” option, otherwise you will need to setup tags manually to promote the changes. It affects only “Tag CI build” stage.

    Full concept of Release Innovator pipeline is based on environments and pipeline tags.

    The appropriate pipeline stage automatically finds the CI build tagged with “UAT-ReleaseName” or “PROD-ReleaseName” and uses its artifact to deploy or update the Aras Innovator.

  4. In Pipeline artifacts, select the CI pipeline build number you want to deploy to UAT.

  5. Click the Run button.

As a result, the Release Innovator pipeline will start, pass “Tag CI build” stage and skip the Deploy SIT stage. The selected CI build is prepared for UAT update and tracked under the defined release identifier.

Environment Promotion Approval

When the pipeline reaches Update UAT stage, it will wait for approval.

  1. Before approving Update UAT stage please make sure that correct CI pipeline is tagged. If you want to deploy to UAT from specific UAT branch, make sure that CI pipeline from UAT branch has “UAT-ReleaseName” tag.

    To review or update tags follow the steps:

    • Open the necessary CI Pipeline

    • Review tags

    • Click Add tags or Edit tags

    • Add new tag

    • Click Save button

    • Review tags

  2. If you are running Release Innovator Pipeline for the first time, make sure that the innovator release name is specified in ReleasePipelineConfigValues group.

  3. If CI pipeline is tagged correctly, click on “1 check in progress”.

  4. Approve the stage.

    “Update UAT” requires approval by “Business Owners” group.

Release Innovator pipeline will trigger the UAT update. You can find link to UAT pipeline inside Queue DeployInnovator on (UAT) and wait for completion step.

  1. To skip Update STG stage make sure that the innovator release name for STG instance is not specified in ReleasePipelineConfigValues group.

Obtain Production Approval

The process of updating PROD environment is similar to UAT update. Before running Update PROD, ensure the corresponding “PROD-ReleaseName“ tag exists on the intended CI build (this is not applied automatically by the pipeline).

“Update PROD” stage requires approvals by “Business Owners” and “GCS Operators” groups.

After approval, the customization is promoted to production with full traceability through release naming, tags, and approval history.