A pipeline is a unidirectional flow that defines the order in which changes will be migrated, starting with the development orgs and finishing in a production org:
You can create a pipeline using the wizard in the Pipeline Manager. Check out the article Creating Pipelines for more information about configuring a new pipeline.
The Pipeline record includes different fields that provide relevant information about your pipeline, such as the repository or the main branch used in the pipeline, as well as fields that enable you to further customize your pipeline and your DevOps process for that particular pipeline. Let’s take a look at the Pipeline record and dig deeper into the fields you can find on the Details tab:
The name of your pipeline.
This checkbox lets you know that the pipeline is active and you can deploy your user stories across the pipeline.
This field shows the Git repository linked to the pipeline.
This field displays the main branch of the Git repository linked to the pipeline, usually master.
Calculate Based on
This field shows the calculation base for the pipeline, which is User Story. This field is used for backward compatibility with older Copado versions.
Specify the type of platform you are creating the pipeline for. E.g., if you are working with Salesforce environments, select Salesforce.
Click on the link in this field to navigate to the Pipeline page.
Advanced Options Section
This checkbox, when selected, enables you to prevent users from committing changes to user stories linked to a particular pipeline.
Order User Stories by
By default, user stories get merged into the promotion branch based on the User Story Reference field in ascending order. You can specify a different user story field with ascending or descending order that Copado will use to define the merge order in this field.
This field enables you to choose the tabs you want to hide on the screen that appears when you click on the promote or back-promote arrows on the Pipeline page.
Exclude From Auto Resolve*
There may be conflicts in certain metadata types that you don’t want Copado to resolve automatically. In this field, you can specify the metadata types whose conflicts should be resolved manually. For more information about this, check out the article Online Conflict Resolution.
Enable Smart Conflict Resolution*
Enable or disable the Smart Conflict Resolution functionality, as desired. This checkbox is selected by default. If enabled, Copado applies the last conflict resolution strategy implemented through the Online Conflict Resolution feature and stored as an attachment in the Git Repository record to all subsequent promotions in the pipeline if the same conflict occurs. If the checkbox is disabled, Copado still stores conflict resolution strategies but does not apply them to other promotions in the pipeline.
Static Code Analysis Settings*
In this field, you can specify the default static code analysis settings that will be used if you run static code analysis on a credential or user story linked to an environment included in this pipeline.
*The fields marked with an asterisk are only available on the Pipeline record page if the platform selected is Salesforce.
Copado DX Section
Enable Copado DX
Select this checkbox if you want to activate Copado DX in the pipeline.
Copado DX Mode
Use this picklist field to define the metadata sources for your scratch org (Git package, Salesforce package, branches or org metadata).
The Automations section is only visible in multi-cloud pipelines.
Promotion Job Template
Lookup field where you can select the promotion template Copado will apply to all promotions linked to the pipeline.
Deployment Job Template
Lookup field where you can select the deployment template Copado will apply to all deployments linked the pipeline.
Commit Job Template
Lookup field where you can select the commit template Copado will apply to all commits to user stories linked to the pipeline.
In this tab, you can add the connections for the different environments in your pipeline.
If you have any projects linked to the pipeline, they will be displayed on this tab.
If you have created a view on the Pipeline page, this view will be displayed under the Views tab.
If you cannot see the related list under this tab, add the Filters related list to the page layout.
In the System Properties tab, you can provide additional values that Copado needs to reference during the promotion or deployment processes (e.g., a Heroku API key).