Add Code Stream pipelines to the Service Broker catalog

As a service administrator, you can make Code Stream pipelines available in the Service Broker catalog by adding a Code Stream 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 Code Stream before you import it. See How do I run a pipeline and see results in Using and Managing vRealize Automation Code Stream.

Procedure

1. Import pipelines from Code Stream.
   1. Select Content and Policies > Content Sources.
   2. Click New, and then click Code Stream Pipelines.
   3. Enter the Name for this content source.
   4. Select the Source project and then click Validate.
      The validation process tests the connection and provides the number of released pipelines that are associated with the project in Code Stream.
   5. Click Create and Import.
   The Content Sources page lists your new source and the number of discovered and imported items.
2. Share the imported items with the source project so that they appear in the catalog.
   1. Select Content and Policies > Policies > Definitions, and create a new content sharing policy.
   2. Enter a name for the content sharing policy.
   3. In the Scope list, select the source project that includes the users who have permission to request the pipelines.
   4. In the Content sharing section, click Add Items and then select one or more pipelines to share with the project.
      You can select all the items imported from a content source or you can select individual items. To select only particular pipelines, select All Content in the Content Sources drop-down menu.
   5. In the Users section, select the users and user groups that you want to have access to the content.
      You can share the content with all users and groups in the project, or you can select individual users and groups.
   6. Click Create.
   The Content Sharing page lists all the items entitled to the selected project. The pipelines are also added to the catalog where the project members can request them.
3. Verify that the pipeline is available in the catalog to the members of the selected projects.
   1. Click Catalog, locate the imported pipeline.
   2. Click Request and provide any required information.
   3. Click Submit.
      The provisioning process begins and the Deployments page opens with your current request at the top.
4. Monitor the provisioning process to ensure successful deployment.
   1. Select Resources > Deployments and locate your deployed catalog item.
   2. Monitor the card status until it is successful.
   You can open the deployment, review the inputs and outputs, use the links to access the output URL, and use the links to the pipeline and execution in Code Stream.

Results

The released pipelines are imported into 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 a Service Broker deployment fails. If you are a Cloud Assembly cloud administrator, you can also do more extensive troubleshooting in Cloud Assembly What can I do if a Cloud Assembly deployment fails in Using and Managing VMware Cloud Assembly.
• If the deployment fails, review the failed execution in Code Stream.
• If you want to control who must approve a pipeline request before it provisions, create an approval policy. See How do I configure 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 a Service Broker icon and request form.