To model your release process, you create a pipeline that represents the stages, tasks, and approvals that you normally use to release your software. vRealize Automation Code Stream then automates the process that builds, tests, approves, and deploys your code.

Now that you have everything in place to model your software release process, here's how you do it in vRealize Automation Code Stream.

Prerequisites

Procedure

  1. Examine the projects available in vRealize Automation Code Stream and select one that is right for you.
    • If no projects are listed, ask a vRealize Automation Code Stream administrator to create a project and make you a member of the project. See How do I add a project in vRealize Automation Code Stream.
    • If you are not a member of any projects listed, ask a vRealize Automation Code Stream administrator to add you as a member of a project.
    Projects in Code Stream
  2. Add any new endpoints that you need for your pipeline.
    For example, you might need Git, Jenkins, Code Stream Build, Kubernetes, and Jira.
  3. Create variables so that you can reuse values in your pipeline tasks.

    Use restricted variables to constrain the resources used in your pipelines, such as a host machine. You can restrict the pipeline from continuing to run until another user explicitly approves it.

    Administrators can create secret variables and restricted variables. Users can create secret variables.

    You can reuse a variable as many times as you want across multiple pipelines. For example, a variable that defines a host machine might be defined as HostIPAddress. Then, to use the variable in a pipeline task you enter ${var.HostIPAddress}.
    Variables in VMware Code Stream
  4. If you are an administrator, mark any endpoints and variables that are vital to your business as restricted resources.

    When a user who is not an administrator attempts to run a pipeline that includes a restricted resource, the pipeline stops at the task that uses the restricted resource. Then, an administrator must resume the pipeline.

  5. Plan the build strategy for your native CICD, CI, or CD pipeline.
    Before you create a pipeline that continuously integrates (CI) and continuously deploys (CD) your code, plan your build strategy. The build plan helps you determine what vRealize Automation Code Stream needs so that it can natively build, integrate, test, and deploy your code.
    How to create a vRealize Automation Code Stream native build... Results in this build strategy...
    Use one of the smart templates.
    • Builds all the stages and tasks for you.
    • Clones the source repository.
    • Builds and tests your code.
    • Containerizes your code for deployment.
    • Populates the pipeline task steps based on your selections.
    Add stages and tasks manually.

    You add stages and tasks, and enter the information that populates them.

  6. Create your pipeline by using a smart template, or by manually add stages and tasks to the pipeline.
    Then, you mark any resources as restricted. Add approvals where needed. Apply any regular, restricted, or secret variables. Add any bindings between tasks.
  7. Validate, enable, and run your pipeline.
  8. View the pipeline executions.
    Viewing the pipeline executions.
  9. To track status and KPIs, use the pipeline dashboards, and create any custom dashboards.
    Viewing the dashboard for a CICD pipeline.

Results

You created a pipeline that you can use in the selected project.

You can also export your pipeline YAML to import and reuse in other projects.

What to do next

Learn about use cases that you might want to apply in your environment. See Common use case examples for vRealize Automation Code Stream.