Skip to main content
Topics#Enterprise ArchitectureSébastien Van Cutsem의 질문
Sébastien Van Cutsem 님이 #Enterprise Architecture에 질문했습니다
2015년 9월 9일 오전 11:24

SalesForce release management - best practice ?

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.
답변 5개
  1. Aleemuddin Khan (AutoRABIT)
    2016년 2월 8일 오후 5:50
    Hi Sebastien,

    This is Aleem from AutoRABIT. I'd recommend you to go through the following link for SVN setup and connectivity:

    https://developer.salesforce.com/page/Using_Force.com_with_Subversion_for_Team_Development

    AutoRABIT has strong integration support for Version Control Systems (SVN, GIT, TFS & Perforce) and can fast-track your Continuous Integration by empowering you with following capabilities:

    a) Fetch uncommitted changes from Salesforce and commit directly to SVN using AutoRABIT.

    b) CI jobs creation from SVN

    c) Easy commit, and Easy Deploy to boost productivity

    d) Compare, sync Salesforce org and SVN

    e) Fetch changes from your repository based on date, revision or tagged check-in’s and deploy them to your Salesforce environment.

    Incase you need further assistance, please feel free to write to us at support@autorabit.com, our Support Engineers will get in touch with you.

    Thanks

    Aleem
답변을 작성하세요...
0/9000