Continuous Integration & Continuous Delivery is the enabler of a true DevOps team

Typically in Salesforce, everything you build revolves around your org. Whether you’re working in a production org with dependent sandboxes or in a developer edition, the canonical source of truth is hosted in your Salesforce environment.

This is different from workflows you may be familiar with if you develop on other platforms, where your source of truth is often a version control system. Modern software development tools have made automated testing and delivery a commodity.

What is Continuous Integration and Development (CI/CD)?

Continuous integration puts a great emphasis on testing automation to check that the application is not broken whenever new commits are integrated into the main branch.

Continuous delivery is an extension of continuous integration to make sure that you can release new changes to your customers quickly in a predictive and repeatable way.



Will add value to:

1. Productivity
2. Time to market
3. Quick Bug Fixes


Will add value to:

1. More time available for adding business value
2. Minimize repetitive tasks

Keep head start to

Will add value to:

1. Focus on new business functions
2. Time to market

Continuous Integration &
Continuous Delivery Model

Continuous Integration & Continuous Delivery is all about seeing the big picture, to consider all aspects that affect the ability to develop and release your Salesforce software.

The end-to-end process of developing and releasing Salesforce software can be a complex and sometimes overwhelming process. It can be difficult for companies to have a clear view on where they are and where they want to be.

For this reason 2ManyDigits created the Continuous Integration
& Continuous Delivery Model. It will give structure and a better understanding of the implementation of a Continuous Intergration & Continuous Delivery process which fits the customer needs.


> Deployments manually
> OTAP – in place
> Apex unit 80% coverage


> Basic deployment scripts
> Use of scratch org
> Automated deployment to test environment
> Apex unit 90% coverage
> Testing manually


> Automated testing for critical processes
> Automated deployment to all environments
> Some deployments outside user-widow
> Apex unit 100% coverages


> Automated testing for acceptance environment
> Integration test in pipeline
> 100% Automated deployments
> Deployments everyday


CICD Levels

Performing CI/CD like a boss can make the DevOps team focus on business change