Branch Orgs are the place you perform feature development. These orgs allow you to work within the 'dealer' namespace but not contaminate the master code branch. A few things to know about Branch Orgs.
- By default they are empty (No metadata yo)
- You can modify stuff that the managed codebase may not actually allow
- It's a great scratchpad. If you break something, only you will notice.
Read this, it should help.
Branch Orgs and Feature Development
If you are ready to prepare your org with a copy of the dealer.master_branch follow these instructions.
First, you will need to have the Force.com Migration Tool (And subsequently ANT) Installed.
Follow these instructions to get it done.
Force.com Migration Toolkit - Installation Instructions
Do yourself a favor and follow the pre-requsites and install ANT.
After you clone this repo onto your machine, some settings will need to be applied to make this work.
Open the build.properties file.
- dt.username = Set your username for the primary managed package here
- dt.password = Set your password and sectoken here
Once you have these settings in place it is time to apply your Branch Org User/Pass.
- sf.username = Set your username for your Branch Org Here
- sf.password = Set your password and sectoken here
Now that your ANT Scripts can authenticate, let's retreive the metadata.
Execute the following command
ant retrievePkgThis will begin the process of downloading a current copy of the package metadata to your local metadata folder.
Execute
ant deployCode to send the metadata up to the Branch Org.This should take about 10 minutes to run, be patient
That should be all. The metadata upload should build a working environment for you.