Skip to main content
AutoRABIT, Inc.

New EZ-Commit

This section allows you to commit your changes from the Salesforce Org to the required Version Control System.

Pre-requisites for using New EZ-Commit

The following pre-requisites are required to use New EZ-Commit functionality:

  1. Salesforce Org Registered with AutoRABIT
  2. Version Control Registered with AutoRABIT
  3. My Profile is mapped with user details for Salesforce Org as well as Version Control
  4. User has permission to perform EZ-Commits

Committing to Version Control

  1. In AutoRABIT home page, click on Version Control > New EZ- Commit. A page will get displayed.

  1. Select a Salesforce Org from the dropdown list.
  2. Select the Author from the list (Based on the org that you have selected, the list of mapped users is displayed). There is option to select All the users.

Note: This option is used to commit changes across the orgs irrespective of the user. It is accessible only to AutoRABIT org admin.

  1. Filter option allows you to specify a date range to fetch changes. See the screenshot below.

  1. Optionally, you can select Additional Metadata. When multiple users make changes to metadata, the last modified date of a Picklist is not updated by Salesforce, so AutoRABIT provides an option to include pick lists. Additional Metadata allows you to select the Metadata Members form Salesforce Org and commit them.

  1. Select the Metadata Type from the drop down field. You can select the required metadata members and commit them.

Note: For multi-picklist, select Picklist from the Metadata Type field and the object; all the existing metadata members will be displayed.

  1. Clicking on Fetch Changes will allow you to see live status updates about the changes that are being fetched from a Salesforce Org.
  2. All the metadata types that have been modified/ added are displayed.

Note: Changes made to the existing metadata or newly added metadata by the selected author are only displayed.

  1. Next, click on Label Type. In Label Type you have option to choose between: None , ALM System, Custom Label and Release Label.

  1. Custom Label: Custom Label helps to label particular commit. For ex: changes related to a user story or task etc, under a specific label. These changes can be picked                            and deployed into various orgs using the label provided from “Start new build” option in the build home page. You can re-use the labels and perform                            multiple commits under a given label. Select the label from the dropdown or create a new one by clicking “+” icon.

  1. Release Label: Release label is the label created by grouping your EZ-commit labels as a release label.
  2. ALM System: Once the changes are committed to the version control system, the status of the ALM work item is updated and reflected in your ALM system.
    • In Label Type, select ALM System, then do the following:
      • Select the ALM type from the drop down box. Currently AutoRABIT supports ALM types like Jira, IBMRTC, Version One, and CA Rally.
      • Select the Project and the Planned for from the drop down list for which the commit is planned.
      • Next, click Go.

  1. Next, click on either:
    1. Validate & Commit
    2. Compare & Commit
    3. Commit

​​​​​​​Validate & Commit

Validate & Commit allows you to validate your commit before committing to Version Control System. This feature even allows you to generate reports before commit such as Static code analysis, code coverage, validate deployment with success, warning and errors, etc.

  • Enter a name in Commit Label name field (no special characters are allowed).
  • Choose a Salesforce Org from Validate on Salesforce Org drop down field.
  • Next, you have three options to choose from:
    • Show Code Level Differences: If checked, it will generate code level difference report between two orgs. You can view the report in Commit Validation History homepage
    • Run Static Analysis: Generates Pre-validation static analysis report. To view the report, go to Version Control > Commit Validation History.
    • Run Apex Tests Dynamically: Generates apex tests report. To view the report, go to Version Control > Commit Validation History.
  • You can also add Apex Test Classes manually. To add, enter the test classes separated by comma and click on Add button.
  • Enter the Reviewer Email Id(s) and comment in their respective field.
  • Next, check Commit Profiles/Permission sets only for the selected metadata if required.
  • Click Proceed for Validation.

​​​​​​​

Compare & Commit 

This option allows you to compare the metadata between the source and destination orgs.

 

Commit

Allows only to commit to Version Control System.

​​​​​​​​​​​​​​

Iconic Representation for Ez- Commit summary page as below:

                        Icon                                                                     Description
vc-09.png

Salesforce Org drop down allows you to select the Salesforce Org from which you want to fetch the changes

vc-010.png

Author drop down allows you to select the Salesforce Org User name of whom you would like to retrieve the changes

vc-011.png

Filter allows you to specify a date range to fetch changes

vc-012.png

Fetch Changes allows you to fetch changes from the Salesforce Org

vc-013.png

Additional Metadata allows you to cherry pick the Metadata Members form Salesforce Org and commit them

vc-014.png

Reset all the selections done with respect to Salesforce Org, Author, Filter, etc.

vc-015.png

Validate & Commit allows you to validate your commit before committing to Version Control System (VCS)

vc-016.png

Compare & Commit allows you to compare the metadata members selected from Salesforce Org to the VCS where being committed. Here you see the differences and commit.

vc-017.png

Commit allows you to commit the changes selected to the VCS

vc-018.png

Label Type allows you to select/create a label and commit them to VCS accordingly

  • Was this article helpful?