You can create, edit, view, copy, and delete the release pipeline. You can have multiple stages for a single release pipeline.

About this task

These pipelines form a single application or a module. You can model a pipeline with multiple stages and tasks in a stage. You can use each to depict the release cycle for an application or a module.

Plug-ins can use binding variables as part of input configurations. These variables are replaced at runtime with the values where they are placed.

The shared pipeline variable is always preceded by the binding variable. For example, ${pipeline.PipelineVariable}.

Prerequisites

  • Verify that you have available predefined vRealize Automation blueprints, workflows, scripts, or test jobs that perform tasks that the pipelines trigger.

  • Verify that the artifacts in the Artifactory server repository are prepopulated so that you can use the Artifact Management capabilities.

  • Verify that the applicable plug-ins and endpoints are registered. See the Installation and Configuration guide.

  • Familiarize yourself with the input and output details required to create tasks.

Procedure

  1. Select Code Stream > Pipelines.
  2. Click Add to create a pipeline.
  3. Enter a name and description for the pipeline.
  4. Click Add to define the input properties for the pipeline.

    These properties are required only if you want to pass certain parameters at the time of triggering a pipeline run. You can reference these parameter values across all stages during modeling. The run time values are applied during the pipeline run.

    Option

    Description

    Name

    Enter a property name.

    Description

    Enter a description for the property.

    Value

    Enter a property value.

    For example, ABC-876541.

  5. (Optional) : Select the first check box if you want this pipeline to run concurrently.

    The pipeline model reuses the same set of virtual machines to deploy a software change. The concurrent run overwrites the deployed change.

  6. (Optional) : Select the second check box and provide the Socialcast Webhook Name and Socialcast Webhook URL to post updates to Socialcast.

    The Socialcast updates are useful to collaborate among team members working on releases and to track pipeline execution status such as pipeline execution start, pause, resume, cancellation, failure, and completion. A new pipeline execution creates a new status message on the Socialcast group and the subsequent statuses of the execution are posted as comments to the message. You can engage yourself in individual threads by adding comments and track the progress of a pipeline execution.

    The name of the Webhook you provide is the name of the group created for communication in Socialcast.

    You can locate the Webhook URL by navigating to Socialcast > Configured Group > Integrations > Codestream > Add > Step 5.

    Note:

    You must have an administrator privilege for the group configured on Socialcast to add the integration and copy the Webhook URL.

  7. Add the email addresses of recipients who receive event notifications during the pipeline execution.

    The email addresses are for the users who have access to the same vRealize Automation appliance.

  8. Enter the applicable tags.

    A tag is useful in grouping pipeline models or runs.

    For example, you can use a tag to filter a pipeline model or run view.

  9. Click Stages to continue pipeline creation.
  10. Click Add Stage to add multiple stages to this pipeline.
  11. Double-click the default stage name and enter a name.

    For example, you can create development, test, QE, and production stages.

  12. (Optional) : Select a stage and drag it to a different place in this pipeline.

    For example, if your pipeline consists of development, test, and QE stages, you can move the test stage after the QE stage.

  13. Click Save as Draft to save the pipeline.
  14. Create tasks for every pipeline stage.

    You can add multiple tasks to a stage and model tasks within a stage to run in parallel. You can drag and drop tasks to run in parallel. Running a parallel task is limited only within a stage. The Artifact, Custom, Deploy, Provision, and Test tasks are supported. Certain tasks might depend on tasks that precede them in the workflow. You can drag tasks up or down depending on the workflow. Tasks are run sequentially or in parallel depending on how you have modelled the tasks within a stage. You can configure a task's input to depend on the output from an earlier task. When you add parallel tasks in a single group and configure the task's input to depend on the output from an earlier task, the variables from the output of the earlier task belonging to the previous group is always considered.