Content pipeline services allow the custom release flow of content to be applied, there are various pre-pipelines or post pipelines that are set up to run that are configured in the Content Settings page. Each pipeline can be run either in the background (asynchronous call) or the whole release flow can stop until the pipeline has completed (synchronous). However, with vRealize Suite Lifecycle Manager 8.0, you can now view the Content Parent and Content capture in two separate views on the Content pipelines page.

Each pipeline is made up of various Stages, each stage then can have various Tasks. Tasks can be either parallel or sequential based on your custom business logic.

Once you have selected 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.

Content pipeline runs pre-stub and post-stub based on run in the background flag. If it is enabled, then a call is not a synchronized call and the content pipeline does not wait for the status of the stub. Similarly, if it is disabled, then the call is a synchronized call and content pipeline does wait for the status of the stub. It takes more time as compared to a disabled background process.
Note: At a time, only 11 content pipelines can run at a time. Some parameters are empty in Lifecycle Manager 2.1 on pipelines stubs. If you still want to use the pipelines, then use the packageVersionLink to retrieve the package version details like packageName, packageType, and so on. And you can also perform similar operation using pre and post-test stubs.