• Vinay Yelavarthi
  • 0 Points
  • Member since 2016

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
  • 1
Today we do not have a release magament process for SFDC releases. I read a lot of articles on the subject but I don't find the best way. There is a lot of tools to do that : Flosum, AutoRABIT, Copado, CloudMax, sfOpticon, Force.com Migration Tool... 
We think to use the Migration tool with SVN and the dataloader to automate all the process and make Continuous Integration with Jenkins. The idea is that we would like to have :
- a sandbox for each developper 
- a sandbox (QA-Integration) to validate the code (SF best practices convention, naming convention,...) 
- a sandbox (UAT) for users tests
- a sandbox (staging) to validate migration to production 
- poduction
What we want to avoid is to take too much time for the prod deployment, found errors in the last step (UAT-staging), found dirty code in another environement than development and we would like to easily roll-back, compare environment, rebase an environment... We think that with the migration tool and svn we can achieve it without encountering too many difficulties but I want to be sure before I implement all the process. So has someone already implemented a similar process in his organization ? Has someone scripts exemple ? If not what do you suggest as a proper process for managing SFDC releases according to our needs ?

Thanks in advance for your answers en your help.