You can add, edit, view, clone, and delete the release pipeline from the Pipelines tab. You can have multiple stages and build IDs 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 within a stage. You can use each to depict the release cycle for an application or a module.

Prerequisites

  • Verify that SSO, OVA, and OVF are installed.

  • Apply the license for release automation.

  • 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 are registered. See Registering Plug-in Instances for Release Pipeline.

Procedure

  1. Log in to the vRealize Automation appliance.
  2. Click Add to create a pipeline.
  3. Enter an appropriate 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 run.

    Option

    Description

    Name

    Enter a property name.

    The name cannot include an underscore.

    Description

    Enter a description for the property.

    Value

    Enter a property value.

    For example, ABC-876541.

  5. (Optional) : Select the check box if you do not 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. Add the email addresses of recipients who receive event notifications during the pipeline run.

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

  7. 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.

  8. Click Stages to continue pipeline creation.
  9. Click Add Stage to add multiple stages to this pipeline.

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

  10. Click Save as Draft to save the pipeline.
  11. Familiarize yourself with the input and output details required to create tasks.
  12. Create tasks for every pipeline stage.

    You can add multiple tasks to 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 move tasks up or down depending on the workflow. Tasks are run sequentially and you can configure a task's input to depend on the output from an earlier task.