ant migration tool for salesforce change control

In some wild and crazy companies, you can go straight to production. Sometimes you deploy to a QA server continuously but have manual checks before production. Now in practice, CI can look quite different depending on the context. When you want to submit a change, automated tests run so you know whether it’s safe to deploy or not and if they pass you automatically deploy your changes to the target environment.

Test automation is also a key component of CI. Typically this involves using a source control solution (Git, SVN, etc.) and a CI server (e.g. Typically, when people refer to CI they mean setting up an automated process that allows each developer or admin to be pushing their changes in real time without stepping on others’ toes.

What are the benefits for Salesforce teams?Ĭontinuous Integration or Continuous Delivery (henceforth just CI) is the idea of automating deployments so that that you can continuously integrate and deliver small changes rather than doing massive releases.

In this post, we’ll try to address the following questions: It’s called Continuous Integration/Continuous Delivery or CI/CD for short. Many wonders: is it possible to make this more automated and cut down on this manual burden?įortunately, there is a way. So what is the slowest, most painful and manual part of the Salesforce development process for most teams?įor many, it’s deployment and delivery of code and configuration changes between environments. You know that automation saves time and headache down the line.

If you read this blog, you’re probably a fan of automation. ** Disclaimer – If you buy Blue Canvas I will not get any commission.

Ant migration tool for salesforce change control