As a service administrator, you can make Automation Pipelines pipelines available in the Automation Service Broker catalog by adding a Automation Pipelines content source and sharing the pipelines. The pipelines are the continuous integration and delivery model of your software release process.
After you import the pipelines, you share them with project members so that they can deploy the pipelines from the catalog. After the pipeline deployment execution completes, the users can access review the inputs and outputs, and use the output, pipeline, and execution links.
Prerequisites
- Verify that the pipelines that you are importing are enabled and released in Automation Pipelines before you import it. See How do I run a pipeline and see results in Using Automation Pipelines.
Procedure
Results
The released pipelines are imported into Automation Service Broker, shared in the catalog, and deployable.
What to do next
- If the deployment fails, click the deployment name and begin troubleshooting. See What can I do if an Automation Service Broker deployment fails. If you are an Automation Assembler cloud administrator, you can also do more extensive troubleshooting in Automation Assembler What can I do if an Automation Assembler deployment fails in Using Automation Assembler.
- If the deployment fails, review the failed execution in Automation Pipelines.
- If you want to control who must approve a pipeline request before it provisions, create an approval policy. See How do I configure Automation Service Broker approval policies. The lease and day 2 policies do not apply to pipelines.
- To provide more or fewer user inputs at request time, you can create a custom form. See Customize an Automation Service Broker icon and request form.