As your Salesforce Organization undergoes heavy customization and frequent builds, moving changes from one Sandbox to other sandboxes starts taking longer time and effort. Also, in normal Salesforce project, there are chances that you will have minimum three sandboxes likely Developer Sandbox, QA Sandbox and UAT Sandbox. After some time you will be in need of some solution which can reduce your effort.
Almost 5 years back, when I was working on .net along with Salesforce, I posted article on Continuous Integration of ASP.net and subversion as a code management with MSBuild on code project.
This time its Salesforce using Jenkins. In this article I will walk through solution of above problem using Jenkins. Don’t forget to watch Video at end of this article, where I provided demo of everything explained in this article.
Prerequisite Software:
- ANT
- Salesforce Migration Tool
- Git
- Eclipse or PuTTYgen to generate SSH key
I am assuming you already know about below concepts:
- How to use Git with Salesforce
- Using ANT migration tool in Salesforce
- Generating SSH key
- Automated Daily Backup of Salesforce Using ANT Migration Tool and GIT (Optional)
I will suggest to get familiar with first three topics before jumping to Continuous Integration.
There are two ways to start working with Jenkins
- Install Jenkins on your local system
- Use Cloudbees online
Below diagram shows complete flow of Continuous Integration we are going to setup in this article.
For this tutorial, I will install Jenkins on my local system. To install it, Navigate to Jenkins homepage and download installer. Continue reading “Continuous integration in Salesforce Using Jenkins and Git | Video Tutorial”