Use VMware Aria Suite Lifecycle to specify content pipeline settings, such as the status of the last 24 pipeline actions.
Pipeline stubs
The pipeline stubs display the status of each action. The content pipeline displays the following status types for each content run:
- Pre-capture
- Capture
- Post-capture
- Pre-test
- Test
- Post-test
- Pre-deploy/check-in
- Deploy/check-in
- Post-deploy/check-in
The check-in term refers to content in a source control endpoint such as Git or BitBucket. You can also view corresponding details for the associated parents pipeline.
The Run tab displays information about all the pipeline runs.
Each pipeline consists of various stages, each of which contains multiple tasks. The tasks are either parallel or sequential actions based on your custom business logic.
When you specify an action 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.
Execute pipeline conditions:
- 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.
- 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.
- 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
VMware Aria Automation 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 work flow in
VMware Aria Automation 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, see
Configure pipeline stub.
| Post-Deploy-Pipeline | Pre-Deploy-Pipeline | Post-Test-Pipeline | Pre-Test-Pipeline | Post-Capture-Pipeline | Pre-Capture-Pipeline |
|---|---|---|---|---|---|
|
|
|
|
|
|
