Updated 11 hours ago by Copado Solutions

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 how to configure 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 this record includes:

  • Pipeline Name: The name of your pipeline.
  • Active: This checkbox lets you know that the pipeline is active and you can deploy your user stories across the pipeline.
  • Git Repository: This field shows the Git repository that is linked to the pipeline.
  • Main Branch: This field displays the main branch of the Git repository linked to the pipeline, usually master.
  • Order User Stories by: By default, user stories get merged into the promotion branch based on the User Story Reference field in ascending order. In this field can specify a different user story field with ascending or descending order that will be used to define the merge order.
  • Calculate Based on: This field shows the calculation base for the pipeline, which is User Stories. This is used for backward compatibility with older Copado versions.
  • Manage Releases: Click on the link in this field to navigate to the Pipeline page.
  • 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 an org credential or user story linked to an environment included in this pipeline.
  • Exclude From Auto Resolve: There may be conflicts in certain metadata types that you don’t want Copado to automatically resolve. In this field you can specify the metadata types whose conflicts should be manually resolved. 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 will be selected by default. If enabled, Copado will apply the last conflict resolution strategy that was 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 will still store conflict resolution strategies, but will not apply them to other promotions in the pipeline.
  • 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).

How did we do?