Skip to content
This repository was archived by the owner on Feb 14, 2018. It is now read-only.

DealerTeam/branch-builder

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Branch Build Scripts

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.

  1. By default they are empty (No metadata yo)
  2. You can modify stuff that the managed codebase may not actually allow
  3. It's a great scratchpad. If you break something, only you will notice.

How do I setup my Branch Org?

Read this, it should help.
Branch Orgs and Feature Development

Cool, let's populate some Metadata!

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.


To populate the metadata

After you clone this repo onto your machine, some settings will need to be applied to make this work.
Open the build.properties file.

Don't forget to copy the ant-saleforce.jar to the build-branch folder

Change the follwing settings

  • dt.username = Set your username for the primary managed package here
  • dt.password = Set your password and sectoken here
These auth controls are for copying the source code from the primary packaging org (PPO).

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

Retrieve The Packaged Metdata

Now that your ANT Scripts can authenticate, let's retreive the metadata.
Execute the following command ant retrievePkg
This will begin the process of downloading a current copy of the package metadata to your local metadata folder.

You still need to apply the metadata to your Branch

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.

About

branch org build scripts based on the Ant Force migration tool

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published