+ Start a Discussion
nokhanokha 

Version control in Force IDE

Hi all, I've been making some tests with Suvbersion plugin in a Salesforce project. I've established the following workflow:

 

  1. Team -> Update
  2. Change code
  3. Team -> Update
  4. Merge (if needed)
  5. Team -> Commit
  6. Force.com -> Save to Server

The problem wih this process is that nothing prevents someone from saving changes to server without commiting in first place.

 

Has someone faced this problem? Any hints on how managing this?

 

Thanks in advance!

Jésica.

Best Answer chosen by Admin (Salesforce Developers) 
metaforcemetaforce

It is usually more of a process discipline rather than finding ways to force your users to commit before things gets saved on the server. Still if you want to enforce it, then a possible approach could be - working in Force.com IDE in the offline/disconnected mode so that all the save operations are executed locally, and then using a script based deployment via the force.com migration tool to promote the local changes to the force.com server.

 

The deployment script can be written in such a way that

 

1. it finds out the diff between the local and the SVN version

2. then commits the locally changed files to SVN

3. then deploy it to the force.com dev/sandbox org

 

Do confirm if that's what you are looking for or else provide more details about the problem.

All Answers

metaforcemetaforce

It is usually more of a process discipline rather than finding ways to force your users to commit before things gets saved on the server. Still if you want to enforce it, then a possible approach could be - working in Force.com IDE in the offline/disconnected mode so that all the save operations are executed locally, and then using a script based deployment via the force.com migration tool to promote the local changes to the force.com server.

 

The deployment script can be written in such a way that

 

1. it finds out the diff between the local and the SVN version

2. then commits the locally changed files to SVN

3. then deploy it to the force.com dev/sandbox org

 

Do confirm if that's what you are looking for or else provide more details about the problem.

This was selected as the best answer
nokhanokha

Thanks metaforce, that's exactly what I was looking for :)