Deployment Flows

Updated 1 month ago by Copado Solutions

A deployment flow defines the path user stories will follow through the release process.

To create a deployment flow follow the steps below:

  1. Click on the Deployment Flows tab in the Copado Change Management application.
  2. Click on New, name the deployment flow, e.g. “My First Flow”, and click on Save.
    You can specify a Git repository and a main branch in order to track your metadata changes in Git. The main branch will be assigned to the last environment of the deployment flow (the environments are added in the next step).
  3. From the Deployment Flow Steps related list, create new deployment flow steps by specifying the source and destination environments.
    If working with a Git repository in the deployment flow, you can specify the branch that will be used to track the metadata changes of the source environment. The branch name is case sensitive and must exist in your Git repository. 

Relevant Fields

Active: If checked, the Branch Management features will be enabled in the deployment flow.

Git Repository: Git repository linked to the deployment flow. All branches of the deployment flow steps must exist in this Git repository.

Main Branch: Main branch of the selected Git repository (e.g. master). This branch will be linked to the last environment of the deployment flow (e.g. production, base package).

Static Code Analysis Settings: Static Code Analysis settings used whenever the analysis is run in org credentials or user stories linked to the environments in the deployment flow.

Block Commits: If checked, committing changes to user stories linked to this deployment flow will not be allowed.

Exclude From Auto Resolve: Conflicts found in the selected metadata types are not auto-resolved by Copado when merging feature branches into the promotion branch. The conflicts can be manually resolved using Copado.

Copado DX Fields

Enable Copado DX: Check this option if you are working with scratch orgs.

Copado DX Mode: Copado DX mode determines the type of metadata source you would like to work with in a scratch org. If you select a certain mode, the rest of the metadata source options will disappear from the available options during the scratch org creation wizard or while loading metadata to your scratch org from the DX Panel.

  • Git Artifacts: If selected, only the Git artifact and patch a release options will be available.
  • Package Artifacts: If selected, only the unlocked packages, second generation packages and patch a release options will be available.
  • Branches: If selected, only branch and patch a release options will be available. Note: Please bear in mind that if your branches have more than 10,000 metadata this option will not work due to a limitation in the Salesforce Metadata API.
  • Org Metadata: If selected, only org and a patch release options will be available. Note: Please bear in mind that if your branches have more than 10,000 metadata this option will not work due to a metadata limit in the mdAPI.


How did we do?