Git Integration for Salesforce

Updated 4 weeks ago by Copado Solutions

Copado is the most flexible and comprehensive Git integration for Salesforce. There are many ways in which Copado integrates with Git, from a simple Git deployment entirely in the cloud, with no software needed, to full featured applications such as Copado Change Management (CCM), which includes Copado Branch Management’s feature (CBM), and Copado Continuous Integration (CCI).

Copado can not only be used to deploy from Git, but also to commit changes into a repository. In this sense, Copado has created a unique Git client that allows admins and configurators to commit their declarative changes in a secure, easy and centralized way.

Below you will find a list of all the different ways you can deploy from Git using Copado as well as information about the differences between the two applications.

Feature

CBM + CCI

CCI

Deploy from Git

Yes

Yes

Incremental deployments

Yes

Yes

Validate deployments

Yes

Yes

Validate merges

Yes

No

Merge and deploy

Yes

No

View differences before deploying them

Yes

No

Pre/post deployment jobs

Yes

Yes

Edit deployments

Yes

Yes

Support for feature branches

Yes

Yes

When to Use Branch Management + Change Management

This is the way recommended by Copado. These two features combined will allow deployments from left to right (from lower environments to higher environments, to production), using Copado Change Management, where all quality gates are established and there is a full traceability of the user stories, but will also allow you to keep in sync the different sandboxes by merging and deploying back to the lower environments (from right to left) using Copado Branch Management. Just by committing changes directly from a user story (US), Copado will create a feature branch for that US, which will then be used in CCM to promote only the approved changes. Copado will handle the branch creation and merges, so that implementing a complete Git flow for Salesforce is possible.

When to Use Continuous Integration

You can start using Copado Continuous Integration once you have implemented the Git flow, meaning all your team members work on a daily basis on a Git platform such as GitHub, where they perform code-review and pull requests, Continuous Integration can be used to deploy approved pull requests. In this scenario, users that used to merge Git branches manually can trigger Copado Continuous Integration just by pushing the merge commit.

Other Ways to Deploy from Git Using Copado

  • When using Copado Change Management, developers will be able to attach commits to their user stories. When the release manager promotes the user stories, Copado will combine all the commits and deploy them.
  • From a Git Repository record, you can create a deployment by choosing a starting and ending commit. Copado will create an incremental deployment of all the affected files as in the ending commit. Finally, you choose the destination org to deploy the files to.
  • You can manually create a Deployment record with a Git Metadata step, where you choose the repository/commit ID, then select the files you want to deploy and the destination org.


How did we do?