This site uses tracking cookies. By using this site, you agree to our Privacy Policy. If you don't opt in, some parts of the site might not function.
Blog
Home / Blog / Salesforce / Working with The Force.com IDE and Subversion (SVN)
05Mar 2013

Working with The Force.com IDE and Subversion (SVN)

About the Author

Carlos Eiroa Carlos Eiroa

Carlos loves writing high-quality object-oriented and functional code, and is a big fan of build tools, automated testing, and continuous integration. Specialized in building custom software applications, including AppExchange apps, in the Force.com SaaS platform. Carlos is a Certified Salesforce Advanced Developer, Certified Salesforce Developer, Certified Salesforce Administrator and Certified Java Programmer.

Comments (4)

John - July 3, 2013

Hi Carlos,

Thanks for your posting. Very useful info. One question I have is are you assuming here that each developer’s Force.com IDE project is tied to their own personal developer org?

Otherwise I am thinking once the developer does a “Synchronize SVN” from their project, any changes pulled down from SVN will cause a ‘build/save’ of any updated assets back into the cloud. “Once you update with new changes from the repository the IDE will automatically deploy them to your org.”

If there are multiple developers working in the same org/sandbox, this could cause problems if an older version of a file in SVN is synced to a new developer’s IDE project which then subsequently overwrites a ‘newer’ file in the cloud that another developer is still working on and has not yet committed.

Have you encountered this scenario before?

Thanks,
Lionel

Reply
Carlos Eiroa
Carlos Eiroa - July 8, 2013

 

Hi John,

That's correct. We assume that each developer will be working on his/her own development environment. We have tried having multiple developers working in the same Sandbox (this happens in cases where the client has only one Developer Sandbox and Developer Orgs cannot be used because of some AppExchange app that cannot be installed in these orgs), and we have encountered the problem you describe. Take a look at my post on Team Development in the Salesforce.com/Force.com Platform for more info on how to organize the development environments.

Regards,

Carlos

Reply
Joel Nylund - July 18, 2013

Hi Carlos,

Great article, one thing we noticed is that the salesforce.schema is outside the source folder, when we click on it in the force.com ide, it seems to show what is on our server, but the file is empty, so we cant commit it to svn.

Is there any trick you have other than manually downloading and uploading it back up?

thanks
Joel

Reply
Carlos Eiroa
Carlos Eiroa - August 6, 2013

 

Hi Joel,

The salesforce.schema file is just a placeholder file. It's used by the Force.com IDE to let you see the database schema (objects and fields), as well as run queries against it. However, it’s not really empty. It you open it with a text editor you will see that it contains the text “place holder.” Therefore it’s a valid non-empty text file and you should have no problem adding it to the repository. I have added it to the code repository in all my projects. Did you by any chance remove the “place holder” text?

Regards,

Carlos

Reply

Leave a Reply