A Deployment Flow defines the path the User Stories will follow through the release process.
To create a deployment flow follow the steps below:
- Click on the Deployment Flows tab in the Copado Change Management application.
- Click on New, name the deployment flow, e.g. “My First Flow”, and click on Save.You can specify a Git Repository and 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).
- From the Deployment Flow Steps related list, create new Deployment Flow Steps by specifying the source and destination environment.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.
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 on 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.