function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
EPSWDEVEPSWDEV 

Sharing code in among two development accounts

Hi,

We have a svn repository that contains 1 custom application. We would like two developers working on this code and both having their own developmental Orgs.

Developer 1 created the application and hence it is available on his org.. How do we accomodate Developer 2 so that the source he downloaded  from SVN can be deployed to his org

Any help is appreciated.

Thanks,

Jigar
Best Answer chosen by Admin (Salesforce Developers) 
JonPJonP
Both developers should install the Force.com IDE for Winter '09, as well as the Subclipse plug-in (allowing Eclipse to connect to a Subversion repository).

Then follow these steps:

1. Developer 1 creates a Force.com project in the IDE, downloading only those metadata components you want to version (i.e. that are part of your application).

2. Developer 1 shares the project to SVN.

3. Developer 2 creates an Eclipse project from the SVN repository, checking out from the location where Developer 1 checked in.

4. Developer 2 adds the Force.com Nature to the Eclipse project. (In Package Explorer, right-click on project, select Force.com > Add Force.com Nature.)

5. Developer 2 configures his Salesforce credentials for the project. (In Package Explorer, right click on project, select Force.com > Project Properties.)

6. Developer 2 pushes the application into his Salesforce organization. (In Package Exporer, right click on the "src" folder, select Force.com > Save to Server.)

You will now have your application in both organizations, connected through the SVN repository.  Whenever one of your developers gets an update from SVN, they will need to make sure to use the Force.com > Save to Server command to push the change into their Salesforce organization.

There is also a Force.com Platform Tutorial on checking out a project from Subversion, which walks through steps 3-6 in more detail.