Starting with vRealize Suite Lifecycle Manager 8.0, there are only Content Pipelines and Capture pipeline are supported. In the Content Pipelines section, under the Pipelines tab, the status of the last 24 pipeline executions can be seen in the Content_Pipeline card. Each of the content pipeline executions when selected, shows the associated Capture pipelines, if any, in the Capture pipeline card. The execution representations, the colored dot in the pipeline card, can be selected to view a detailed breakdown of the various stages of the selected execution. The Content pipeline execution can contain a maximum of nine stages in the order of execution. However, the actual execution has the stages which are relevant to the execution.

Pipeline Stubs

The pipeline stubs display the status of each action whenever a content is captured. The content pipeline has the following status types whenever a content is run.
  • Pre-Capture
  • Capture
  • Post- Capture
  • Pre-Test
  • Test
  • Post-Test
  • Pre-Deploy/Checkin
  • Deploy/Check-in
  • Post-Deploy/Check-In
In the last three stages, the term Check-in is used if the content is released to a source control endpoint such as Git or BitBucket else the term deploy is used. By default, the pre or post stages are disabled and should be configured before they can be used in an execution. The configuration and various modes of execution for pre or post stages, also called pre or post stubs, are covered under the configure pipeline stubs section. The capture pipeline will always have a single stage, that is Capture. The corresponding details of the pre or post capture can be viewed in the associated content pipeline, also referred as the parent pipeline.

The Executions tab lists all the content and capture pipeline executions. The list shows the status, time taken, executed by and time of the request for each of the executions. This list can be filtered by the type of pipeline and execution status.

Each pipeline consists up of various Stages, each stage then can have various Tasks. Tasks can be either parallel or sequential based on your custom business logic. After selecting an action that you want to perform on a content, a content capture can list various types of status related to such an action. Each of the content settings is related to the view displayed on the Content Pipeline page.
Note: At a time by default, only 15 content pipelines can run and at most six simultaneous captures for each of vRealize Automation, vRealize Operations Manager, and vRealize Orchestrator source control content categories. For vSphere, only one capture is executed at a point in time.

Execute Pipeline Conditions:

  1. EXECUTE_ON_SUCCESS - The stub is executed only if the corresponding stage executes successfully. For example, Post-Capture if configured to EXECUTE_ON_SUCCESS executes only if the Capture stage is executed successfully.
  2. EXECUTE_ON_FAILURE -The stub is executed only if the corresponding stage execution fails. For example, Post-Capture if configured to EXECUTE_ON_FAILURE executes only if the Capture stage is execution fails.
  3. EXECUTE_ON_SUCCESS_AND_FAILURE - The stub is executed irrespective of whether the corresponding stage execution passes or fails. For example, Post-Capture if configured to EXECUTE_ON_SUCCESS_AND_FAILURE executes in both cases, whether Capture stage execution passes or fails.

Inputs Parameters

The pre or post stubs support the mentioned list of parameters, the values of which can be passed to the respective vRealize Orchestrator workflow as inputs. The value of these inputs depends on the content (been captured/tested/deployed) of the pipeline execution for which the pre or post routines are executed. Currently, all the parameters are of the type 'String'. Therefore, the input parameters configured for the corresponding workflow in vRealize Orchestrator should be necessarily of type 'String'. A mismatch between the type of parameters results in an execution failure for the pipeline. For more information on configuration, see Configure Pipeline Stub.
Post-Deploy-Pipeline Pre-Deploy-Pipeline Post-Test-Pipeline Pre-Test-Pipeline Post-Capture-Pipeline Pre-Capture-Pipeline
  • contentName
  • contentEndpoint
  • ContentId
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • status
  • requestedby
  • useridentity
  • contentName
  • contentEndpoint
  • ContentId
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • requestedby
  • useridentity
  • contentEndpoint
  • ContentId
  • contentName
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • requestedby
  • useridentity
  • contentName
  • contentEndpoint
  • ContentId
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • requestedby
  • useridentity
  • contentName
  • contentEndpoint
  • ContentId
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • requestedby
  • useridentity
  • status
  • contentName
  • contentEndpoint
  • ContentId
  • contentType
  • ContentVersionID
  • requestid
  • requestnumber
  • requestedby
  • useridentity