You need to sign in to do that
Don't have an account?
Ken Koellner
Source Control policy for developers working in the same sandbox
Does anyone --
Has anyone solved this problem and devised a strategy for using source control when multiple users are working in the same sandbox?
- develope with a team of at least 1/2 dozen developers.
- Have a large org with lots of code and complex data that must be setup before any real work can be done.
- Use a single development sandbox for all developers.
- Use a source control for code.
Has anyone solved this problem and devised a strategy for using source control when multiple users are working in the same sandbox?
You are using Git probably.
http://gitolite.com/gitolite/locking.html#
https://www.packtpub.com/hardware-and-creative/gitolite-essentials
https://github.com/sitaramc
That would be interesting if someone has already used the locking of file with gitolite or SVN instead of using Git basically and could give the feedback here.
Apache Subversion (svn) is an interesting alternative to Git with its lock communication.
Lock Communication: http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html
SVN versus Git: https://svnvsgit.com/
If you have 1/2 dozen developers, I don't think you can avoid source control, it is probably the only option that works. Having said that, leveraging source control comes with overhead and the unique declaritive aspect of Salesforce makes this even more challenging.
I wrote a blog on things that I've learnt working with Salesforce & source control for the past 6 years. Hope this helps.
https://medium.com/@clickdeploy_team/salesforce-release-management-best-practices-4255ad7c7f63