DevOps for Salesforce – Tools, Processes and Flow
In this Blog, we will see how DevOps can be applied in Salesforce Development.
Here, Let’s understand ‘HOW’.
Please refer DevOps Introduction topic if you want to revise the basics.
Ok, DevOps for Salesforce is much as similar to Enterprise platform development (Java, .Net, ERP etc). Only difference is Salesforce is Cloud and deals with various sandboxes.
We need to first identify the DevOps tools which can be used to adopt DevOps transformation.
Some of the tools which can be helpful are shown in this diagram
So, How does DevOps for Salesforce work?
Start with the coding, Let’s understand step by step:
Step 1: Developers pulls the code to feature branch from Master GitHub
Step 2: Developers pulls down to local environment (Dev Sandbox)
Step 3: They do the changes and unit test and push the code to feature branch ( STG Sanbox) and creates new Integration Points which is visible to other developers working in local.
New Integration point
Step 4: Other developers completed their codes and push to STG and creates new Integration points
Step 5: All the integrated features then get push to Project level branch (say ‘INT’ branch) and creates new Integration points.
Step 6: All Integrated features get pushed to UAT for Automated testing
Step 7 : Tested code moves to Production
Hope, this clears the Code branching, integration and build process.
If you prefer using Eclipse the high level flow would look like
In short, Developers do the changes in local and push to Git. Jenkins Git plugins, you can build and deploy the code and run the automated testing.
Please refer Salesforce Bitbucket EGIT Version Control Blog for Hands-On Implementations.
Wish you the best and Happy Reading!
All data and information provided on this site is for informational purposes only. thearsana.com makes no representations as to accuracy, completeness, correctness, suitability, or validity of any information on this site and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use. All information is provided on an as-is basis.