A release pipeline is a collection of stages where each stage represents a deployment environment. For example, the development, test, user acceptance test (UAT), load test (LT), systems integration testing (SIT), and staging environments that a software change has to pass through independently before it is released.

Sample Release Pipeline with Stages

Sample stages of a release pipeline model

The number of stages and configuration of each of these stages varies based on the application, and whether the release is major, minor, patch, or organization release policies.

Video icon Modeling a Release Pipeline Template (http://bcove.me/zgy163u6 ).

To track your work as you complete the modeling tasks, complete the tasks in the order they are given.


You can create, edit, view, copy, and delete the release pipeline. You can have multiple stages and build IDs for a single release pipeline.


An artifact task lets you search the library of binaries in different Artifactory repositories that you can deploy on a virtual machine.


You can use a custom script task to run a script that resides on a remote host for any task. After the script runs, you can monitor the script progress and capture the script response, which you can pass as input to other release pipeline tasks.


With a custom task, you can start a custom activity with a vRealize Orchestrator workflow. This activity can also be a manual approval.


A service blueprint task lets you invoke a plug-in available in the vRealize Automation service catalog from a release pipeline. You can publish a predefined workflow from vRealize Orchestrator to the vRealize Automation service catalog.


You can use the Team Foundation Server task to connect to the Team Foundation Server and invoke configured build and test jobs.


A deploy task deploys or updates the existing artifacts on the machines.


A provision task provisions machines. When you register a vRealize Automation, vRealize Code Stream starts a local or remote vRealize Automation 6.1. or 6.2 instance to provision infrastructure in a specific environment.


You can use a test task to test a deployment. When you register a Jenkins Server endpoint, you connect to a Jenkins server to start a build job from a release pipeline.


Gating rules are a set of criteria that each stage must pass to proceed to the subsequent stage. You can configure gating rules based on your requirement for a pipeline.


You can run a release pipeline that is activated. After you activate the release pipeline, pipeline modeling is complete and you can run it.