You can run a release pipeline that is activated. After you activate the release pipeline, pipeline modeling is complete and you can run it.
About this task
You can view a release pipeline run on the Pipeline Executions tab. The draft state signifies that the Release Manager is still modeling the release pipeline.
Multilevel information is provided during the release pipeline run.
Level 1.Status at release pipeline level which is the description of the current activity.
Level 2. Status at the task or stage level that displays the current task progress and the executed task status.
Level 3. Provides detailed information at task level.
Verify that a release pipeline is created in a draft state. See Create a Release Pipeline.
Verify that predefined vRealize Automation blueprints, workflows, and scripts are created, and test jobs that perform tasks that the pipeline can trigger.
Verify that artifacts are available in the Artifactory server repository to use the vRealize Code Stream Artifact Management capabilities.
- Click the Code Stream tab.
- Select an existing pipeline to configure from the Pipeline tab.
- Click Activate to create a vRealize Orchestrator workflow.
Every time a pipeline is activated, a new version of the pipeline is created.
A list of the available pipelines appears.
- Select the pipeline.
- Click Execute.
The Execute Pipeline dialog box appears.
- Enter the description and properties.
- Click OK to run a release pipeline.
If you are running a pipeline with Team Foundation Server 2015 (TFS), you can cancel the pipeline execution and view the status of the configured build in the server. If you are running a pipeline with TFS 2013 and cancel the pipeline execution, the pipeline is marked as cancelled, but the configured build in the TFS server will still display the status of the pipeline as completed.
After a custom script task runs, the EXECUTION_ID_FOLDER run folder is created in the Script_Name_RUN folder. This folder contains the logFile, responseFile, exitStatusFile files, and a clone of the actual script that is being run. For example, script_params.txt, script_log.txt, script_response.txt.
What to do next
You can track the status of the pipeline and troubleshoot failed pipelines. See Using the Experimental Release Dashboard Feature.