CI Jobs with ClickDeploy

CI Jobs are used to automate your release process. These all require a git repository and an Enterprise license. These CI/CD jobs will test, validate, or deploy your metadata. All are based on a trigger or a schedule. The following are setups customers can create for their DevOps within ClickDeploy Enterprise:

1. Deploy to a Salesforce Org

ClickDeploy has the ability to automatically deploy metadata changes to a Salesforce Org. This CI Job requires the setup of a webhook with your git repository. In simple terms, a webhook allows for ClickDeploy to listen and wait for changes to be made in your repository’s branch. Once a change is made, ClickDeploy can grab that change and deploy its metadata to a Salesforce org.

1. Admin & Developer select Metadata and deploy changes through ClickDeploy.
2. ClickDeploy creates a feature branch with committed metadata in the client’s git repository.
3. On release day, Team Lead merges the feature branch (and others) to the org’s branch.
4. ClickDeploy detects the change in the org’s branch via the webhook and deploys those changes to the Salesforce org.

2. Pre-Deployment Validations

There are instances where you would not want to automate deployments to your Salesforce Orgs. Instead of deploying, ClickDeploy will run a validation to see if the Salesforce Org will accept the metadata. Now a release manager can simply deploy once they are ready — after reviewing the test results.

1. Admin & Developer select Metadata and deploy changes through ClickDeploy.
2. ClickDeploy creates a feature branch with committed metadata in the client’s git repository.
3. On release day, Team Lead merges the feature branch (and others) to the org’s branch.
4. ClickDeploy detects the change in the master branch, via the webhook, and validates those changes to Production org.
5. Once that metadata is validated and needed in the Production org, Team Lead selects to Deploy within the ClickDeploy CI Job.

3. Scheduled Backup Deployments

Backing up metadata via a snapshot commit to git is a good idea in case a release creates instability in a Salesforce Org. In ClickDeploy, you can set up a backup from a Source Org to any target branch. You may want to have this scheduled to a specific branch that can be deployed if a rollback needs to occur.

4. Scheduled Validations

Some users may want to take a pulse of the difference between two orgs metadata. ClickDeploy allows a CI Job to be set that will simply determine if all an org’s metadata will be allowed to be merged to a target org. This is more of a high level view and will help see if an org is drastically different or behind its target.