Get prepared for Salesforce DX with our guide to version control for Salesforce
Jason Mann on June 14th 2018
Source-driven development is at the heart of modern Salesforce release management. Shifting the source of truth from the org to version control is the foundation on which DX is built, vital for letting developers build collaboratively and deliver continuously.
If you or your team are looking to harness the full power of Salesforce DX, make sure you have your version control strategy in place before you get started.
We can help you do just that with our practical guide to implementing git-based release management. In our whitepaper we examine how version control works, the benefits of version control over in-org development, and introduce a best-practice model for adopting version control in your business.
A practical guide to version control for Salesforce teams
As a Salesforce tooling partner, our users often ask us to provide input on how they can improve their current workflow using Gearset. Common goals are to speed up deployments, reduce errors and manual tasks, improve reporting, and make collaboration more effective. For many teams, version control is at the heart of the solutions we propose. As version control is not a widely adopted technology in the Salesforce development world, we often get asked questions on how to structure such a process.
Common questions that crop up are:
- What are the main benefits of version-controlled development?
- What does a good version control development process look like?
- How should we structure our repository and branches?
- How do we track and integrate hotfixes back down the development path?
- What metadata should be stored in version control?
- Where should continuous integration be employed, and when should deployments be manual?
- How does Gearset integrate into a version control driven development process?
While there are many guides to version control out there, few provide practical advice on implementation, and fewer still are focused specifically on Salesforce and the nuances of working on the platform. Gearset has been advocating version control for Salesforce development since our inception, so we decided to write a whitepaper to answer these questions and provide an in-depth guide on how to create a best-practice development model in your business.
A resource for the whole team
Our whitepaper was created to be a resource for anyone involved with the administration, development, maintenance, or management of Salesforce environments, looking for ways to improve the cadence, simplicity, reliability, and auditability of their release management.
From the fundamentals of version control through to a detailed release management model for teams of all sizes, it contains best-practice advice for developers, administrators, team managers, and technical architects alike.
If you are thinking about adopting version control, looking for ways to streamline your current development flow, or simply wanting to understand the benefits of version control over sandbox development, this whitepaper is for you.
<a href="/assets/version-control-for-salesforce-whitepaper.pdf" target="_blank" rel="noopener"><img src="/images/blog/whitepaper-guide-to-implementing-version-control-for-salesforce/whitepaper-blog-screenshot-4.png" class="center-no-stretch" alt="The Gearset whitepaper gives an in-depth model for implementing version control driven development for your business"></a>
A good process needs a good deployment tool
The ability to quickly and reliably deploy metadata between Salesforce and version control is crucial to a modern, Agile development flow that Salesforce DX promotes. If you’re looking for a tool which perfectly complements your new release process, you can start a free 30-day trial of Gearset at https://gearset.com or contact us at [email protected] for more information.