Branching baseline is used to retrieve and commit metadata from a Salesforce org to the mapped version control system.
How to create a new Branch Baseline?
To create a new Branch Baseline:
- Log in to your AutoRABIT account. Go to your Admin Menu, then click on Branching Baseline.
- In the next page, click on New Branch Baseline at the top-right side of the screen.
- On the next pop up screen, give a Label name and select a Salesforce org from the list.
- Select the Repository into which the changes must be committed. The repositories displayed are the ones mapped to the Salesforce org in Version Control Repositories section.
- Choose a Branch in the repository.
- Additional Option:
- Exclude baseline managed package changes: If a managed package is installed in a Salesforce org on a date, but a different date is given on the CI Job created, then the installed managed package numbers are also loaded. To skip those installed managed packages, we have an option to exclude baseline managed package changes.
- Delete existing metadata and commit new changes: The process will delete all existing metadata and commit all the metadata members from the Salesforce org to the Version Control repository.
- Click OK. After the branch is created, it is displayed in the summary page.
There are also several operations you can do in Branching Baseline summary page:
- Click Revision Info to view the revision history.
- Click Log to view the entire log of the branch created.
- Click History to view the history of the branch, to get details on all the modifications done to the branch.
- Click Re-Run to, overwrite new content in the existing branch. Here you have options to exclude baseline managed package changes and delete existing metadata and commit new changes.