Copado Continuous Integration

Updated 1 week ago by Copado Solutions


Copado Continuous Integration is an extension of the existing Copado feature set. This feature is designed to help customers better manage the integration with Git repositories, Apex code and other metadata that is deployed to the various Salesforce orgs.

Continuous Integration Entities

Continuous Integration

A Continuous Integration represents a link between a Git repository branch and a destination Salesforce org to which information from the Git repository should be deployed.

Continuous Integration Permissions

This option allows you to set who can execute the CI process or who has read-only access. From this object, it is also possible to set up notifications upon build/validate failure/success. 

Build Task

A build task is created for each execution as a result of a CI record. The build task is also linked to the deployment. A build task record is also created when the CI is run and no changes are detected by Git.


A deployment is a basic entity within Copado and has been part of the application from version 1. However, with CCI a new step type called Git MetaData is included, which reads the metadata from a Git repository instead of a Salesforce org. Build tasks automatically create deployments with a Git MetaData step.

Git Repository

Git repositories within Copado store the necessary information to connect to a Git repository. This entity allows you to create a connection to a Git repository via HTTPs or SSH keys authentication.

Continuous Integration Use Case

Let’s say you have a training org that is being used by your new sales team members. This org is not part of the pipeline, however, you may want to keep the org updated with the latest changes. Copado Continuous Integration will be notified when the UAT or master branches have new changes, and these will be automatically deployed to the training org.

How did we do?