Pipeline stubs are used to support the pipeline extensibility use case in content-management. The pipeline process can be extended by adding a custom logic in pre or post stages of capture, test, or deploy. The custom logic can be created as a vRealize Orchestrator workflow, which can then be mapped to a pre or post stub. Pre and Post stubs are executed before and after, respectively for a given stage.
The content pipeline supports the pre or post stubs:
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.
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 15 content pipelines can run at a time. Some parameters are empty in Lifecycle Manager 8.0 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.