Add a production pipeline configuring-production-pipelines
Learn how to use Cloud Manager to create and configure production pipelines to deploy your code. If you would first like a more conceptual overview of how pipelines work in Cloud Manager, see CI/CD Pipelines.
Overview overview
Using the Pipeline Settings tile in Cloud Manager you can create two different types of pipelines.
- Production Pipelines - A production pipelines is a purpose-built pipeline made of a series of orchestrated steps to take source code from your Git repository all the way into production.
- Non-Production Pipelines - A non-production pipeline primarily serves to run code-quality scans or to deploy source code into a development environment.
This document focuses on production pipelines. For details on how to configure non-production pipelines see the document Configuring Non-Production Pipelines.
The Deployment Manager role is responsible for setting up the pipeline. Pipeline configuration consists of:
- Defining the trigger that starts the pipeline.
- Defining the parameters controlling the production deployment.
- Configuring the performance test parameters.
Add a new production pipeline adding-production-pipeline
After you have used the Cloud Manager UI to set up your program and have at least one environment, you are ready to add a production pipeline.
-
Log into Cloud Manager at and select the appropriate organization and program.
-
Navigate to the Pipelines card from the Program Overview page.
-
Click +Add, then select Add Production Pipeline.
-
The Add Production Pipeline dialog box opens to the Configuration tab where a number of options for your pipeline must be defined. These options are grouped into collapsible sections and are described in the following steps.
-
Provide a descriptive name for your pipeline in the Pipeline Name field.
-
Under the Source Code section, you define where the pipeline retrieves the code it processes.
- Repository - Defines which Git repo the pipeline should retrieve the code.
note tip TIP See the document Program Setup to learn how to add and manage repositories in Cloud Manager. - Git Branch - Defines from which branch in the selected pipeline should retrieve the code.
- Code Location - Defines the path in the branch of the selected repo from which the pipeline should retrieve the code.
-
Under the Environments section, you define what triggers a deployment and how it should be rolled out per environment.
-
In the STAGE section, you can define how the pipeline rolls out to your staging environment.
-
Deployment Trigger - You have the following options to define the deployment triggers to start the pipeline.
- Manual - Start the pipeline manually using the Cloud Manager UI.
- On Git Changes - Start the CI/CD pipeline whenever commits are added to the configured Git branch. With this option, you can still start the pipeline manually as required.
-
Important Metric Failures Behavior - During pipeline setup or edit, the Deployment Manager has the option of defining the behavior of the pipeline when an important failure is encountered in any of the quality gates. The available options are:
- Ask every time - The default setting and requires manual intervention on any important failure.
- Fail Immediately - The pipeline is canceled whenever an important failure occurs. It is emulating a user manually rejecting each failure.
- Continue Immediately - The pipeline proceeds automatically whenever an important failure occurs. It is emulating a user manually approving each failure.
-
-
-