To model your release process, you create a pipeline that represents the stages, tasks, and approvals that you normally use for releasing your software. Automation Pipelines then automates the process that builds, tests, approves, and deploys your code.
Now that you have everything for modeling your software release process, here's how you do it in Automation Pipelines.
- Verify whether any cloud-based and remote on-premises endpoints are already available. In Automation Pipelines, click Endpoints.
- Learn about native ways that you can build and deploy your code. See Planning to natively build, integrate, and deliver your code in Automation Pipelines.
- Determine whether some of the resources that you will use in your pipeline must be marked as restricted. See How do I manage user access and approvals in Automation Pipelines.
- If you have the user role or the viewer role instead of the administrator role, determine who is the administrator for your Automation Pipelines instance.
- Examine the projects available in Automation Pipelines and select one that is right for you.
- If no projects appear, ask a Automation Pipelines administrator who can create a project and make you a member of the project. See How do I add a project in Automation Pipelines.
- If you are not a member of any projects listed, ask a Automation Pipelines administrator who can add you as a member of a project.
- Add any new cloud-based and remote endpoints on premises that you need for your pipeline.
For example, you might need Git, Jenkins, Automation Pipelines Build, Kubernetes, and Jira.
- If you add a remote on-premises endpoint, such as a GitHub repository that is on premises, add a cloud proxy in Automation Assembler. Automation Pipelines can then connect to the endpoint.
A remote endpoint can be a data source, repository, or notification system that resides on premises instead of in a cloud-based environment. On-premises endpoints are not reachable over the public Internet because they reside behind a firewall.
- To add a cloud proxy, download the cloud proxy OVA, and install it in your vCenter instance.
- Go to your Automation Assembler service, click Cloud Proxies, click New, and install the cloud proxy.
- Create variables so that you can reuse values in your pipeline tasks.
Use secret variables to hide and encrypt sensitive information. Use restricted variable for strings, passwords, and URLs that must be hidden and encrypted, and to restrict use in executions. For example, use a secret variable for a password or URL. You can use secret and restricted variables in any type of task in your pipeline.
To constrain the resources used in your pipelines, such as a host machine, use restricted variables. 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 can be
HostIPAddress. To use the variable in a pipeline task, you enter
- 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.
- 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 Automation Pipelines needs so that it can natively build, integrate, test, and deploy your code.
How to create a Automation Pipelines native build Results in this build strategy Use one of the smart pipeline 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, add tasks, and enter the information that populates them.
- Create your pipeline by using a smart pipeline 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.
- Validate, enable, and run your pipeline.
- View the pipeline executions.
- To track status and key performance indicators (KPIs), use the pipeline dashboards, and create any custom dashboards.
You created a pipeline that you can use in the selected project.
You can also export your pipeline YAML, then import it and reuse it in other projects.
What to do next
Learn about use cases that you might want to apply in your environment. See Tutorials for using Automation Pipelines.