Skip to main content
AutoRABIT, Inc.

New Deployment

There are 8 types of deployments in AutoRABIT using:

  1. Salesforce Org 
  2. AutoRABIT build
  3. Package.xml
  4. Metadata Zip
  5. Version Control
  6. Version Control Revision
  7. Commit Label
  8. Release Label

1. Deployment via Salesforce Org

Please follow below steps to perform a deployment from Salesforce Org to Salesforce Org.

  1. From the menu, select Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. Give a label name in the Deployment Label field.
    2. In Deployment From, select Salesforce Org from the drop-down list.
    3. Set Metadata Types to one of the following: (For more information about Metadata, go to Metadata Types section)
      1. All
      2. Full Profiles
      3. Full Permission Sets.
    4. Select Source Org from the drop-down list.
    5. Select Destination Org from the drop-down list.
    6. In Deployment Type, choose between Selective and Full Deployment.
  3.  You can fill the remaining field under Metadata Filter or you can simply ignore. It is optional.
  4. At the bottom of the page, click on Retrieve Metadata (Pre-destructive changes and Post destructive changes is discussed later.)

Selective Deployment

Selective deployment enables you to promote only the selected metadata types in a Salesforce Org.

  1. Choose Selective Deployment in Deployment Type.
  2. Click Retrieve Metadata at the bottom of the screen.
  3. A new page appears which displays the deployment information on the left side and list of all intended metadata on the right side of the screen.

image.png

  1. Next, select the metadata members to carry out the deployment. Also, you can use the Search filter to find any specific metadata.
  2. Compare Orgs & Deploy provide you an option to validate the deployment; to check if the deployment would be successful or not. Once a list of all the metadata members is displayed, select the members that you want to deploy and click Compare Orgs & Deploy.

21.jpg

  1. The metadata is fetched from the destination and the metadata differences are displayed.
  2. Click on a log to see the difference report of a metadata member.

  1. Click Deploy and choose the required filters.

Option Description
Ignore warnings Warnings are generated for a few metadata types during the retrieval process. The components are then uninstalled in the Salesforce server, and during the process few more warning messages occur. But AutoRABIT deploys almost all of the metadata types.
Validate only The label is validated and saved without being deployed. It is saved and can later be used in Quick Deploy.
Take backup Changes are made to the destination org during the deployments. If the deployment fails or has some functional issues, (the issues maybe in the application or due to the failure/success of a build), you have an option to revert back to the original metadata.
Ignore missing visibility settings while deploying profiles While deploying Profile/Permission set, AutoRABIT compares the source and destination orgs and filters the package manifest to keep, only the settings that are common between both (source and destination); it then delivers the package to destination for a perfect deployment.
 
  1. Next, choose an apex tax class from the Test Level drop down field. By default, you have 4 tax class to choose from:
    1. No Test Run
    2. Run All Tests in Org
    3. Run Local Tests
    4. Run Specified Tests

Note: In Test Level, you can select a test type to run after a deployment has been successful.

No Test RunBuild is deployed without running any test cases.

Run All Tests In OrgAll tests are run. The tests include all tests in your organization, including tests of managed packages.

Run Local TestsAll tests in your organization are run, except the ones that originate from installed managed packages. This test level is the default for production deployments that include Apex classes or triggers.

Run Specified Tests: This option allows the user to run specific Apex test classes post deployment.

  • Click OK.
  • Deployment summary is displayed, which contains a list of all the metadata types and members that are being deployed.
  • Next, click on Deploy button.

Full Deployment

Full promotion promotes all the objects of a Sales Org. During the retrieval of metadata from a build, few metadata types cannot be retrieved from Salesforce like, dynamic package .XML files.

Warnings are generated for a few metadata types during the retrieval process. The components are then uninstalled in the Salesforce server, and during the process few more warning messages occur. But AutoRABIT deploys almost all the metadata types.

Metadata Types

There are three types of metadata available for the deployment:

  1. All
  2. Full Profiles
  3. Full Permisision Sets

Full Profiles Metadata

1.jpg

  1. Choose Full Profiles from the Metadata Type(s) dropdown list.
  2. Select Include Field Accessibilities option if you want to deploy all Layouts and Record Types along with full profiles.
  3. After completing the remaining field, click on Retrieve Metadata at the bottom left of the screen. A new pages appears which displays the Metadata types and Profile information.
  4. Once a list of all the metadata members is displayed, select the members that you want to deploy and click Compare Orgs & Deploy.
  5. A new page appears which displays the Layout, Profile and Record Type information required for deployment. 

(Note: You can deploy Layout and Record Type only if you select Include Field Accessibilities in the Metadata Type option. See the attached screenshots for  more information.)

  1. Lastly, click on Deploy button. 

 

Full Permission Sets

Full Permission sets will display set of permissions that is used to grant additional access to one or more users without changing their profile or reassigning profiles.

  1. Choose Full Permission Sets from the Metadata Type(s) dropdown list.
  2. Complete the remaining fields and click on Retrieve Metadata.
  3. You can see the Metadata members based on the permission sets.

 

Pre-Destructive changes and Post- Destructive changes

A. Pre-Destructive changes

Pre-Destructive changes allows users to remove the selected members from your destination and proceed with deployment.

  1. From the menu, select Deployment > New Deployment.
  2. Complete the fields under Deployment Details section and click on Pre-destructive changes at the bottom of the screen.

  1. You will be directed to a new page where you need to select the required Metadata Type.

  1. All the respective metadata members will be displayed. Select the required metadata members and click on Save. Once saved, the selected members will run as part of the Pre-destructive changes.

B. Post-Destructive changes

Post-Destructive changes allows users to remove the selected members from your destination post when the deployment is completed successfully.

  1. From the menu, select Deployment > New Deployment.
  2. Complete the fields under Deployment Details section and click on Post-destructive changes at the bottom of the screen.

  1. You will be directed to a new page where you need to select the required Metadata Type.

  1. All the respective metadata members will be displayed. Select the required metadata members and click on Save. Once saved, the selected members will run as part of the Post-Destructive changes.

 

2. Deployment via AutoRABIT Build

Please follow below steps to do a Deployment from AutoRABIT Build to Salesforce Org.

  1. From the menu, select Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. Give a label name in the Deployment Label field.
    2. In Deployment From, select AutoRABIT Build from the drop-down list.
    3. Choose Project Name and Build No from the drop down list.
    4. Select a Destination Org.
    5. In Deployment Type, choose either Selective Deployment or Full Deployment.
    6. Click on Retrieve Metadata.

 

3. Deployment via Package.xml

The package.xml file, also known as the project manifest, is a control file that determines the set of metadata components (metadata types and members) to retrieve and deploy metadata from one org to another.

By using this you can upload your selected metadata types and members, you don’t have to traverse for selection of metadata types and members

Note: Please avoid the wild cards in package.xml for successful retrieval and deployment of metadata.
  1. From the AutoRABIT homepage, click on Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. Give a label name in the Deployment Label field.
    2. In Deployment From, select Package.xml from the drop-down list.
    3. In the succeeding pop-up, upload a package.xml file.

  1. In Metadata Types, choose the metadata you want to deploy.
  2. Choose a Source and Destination org.
  3. Go ahead with either Selective Deployment or Full Deployment.

 

4. Deployment via Metadata Zip

AutoRABIT provides you an option to upload zip file and deploy to the sandbox using Metadata Zip facility.

  1. From the menu, select Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. In Deployment Label, give a label name.
    2. In Deployment From select Metadata Zip.
    3. In the succeeding pop-up, upload a zip file.

Note: Make sure you read both the notes (Note 1 and Note 2) before uploading any zip file.

  1. Choose a Destination Org.
  2. Go ahead with either Selective Deployment or Full Deployment.
  3. Click on Retrieve Metadata.

 

5. Deployment via Version Control

Please follow below steps to do a Deployment from Version Control to Salesforce Org.

  1. From the menu, select Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. Give a label name in the Deployment Label field.
    2. In Deployment From, select Version Control from the drop-down list.
    3. Select a version control, repository, and the branch from which the metadata has to be deployed.
    4. Set Metadata Types to one of the following:
      1. All
      2. Full Profiles
      3. Full Permission Sets.
    5. Choose a Destination Org.
    6. Go ahead with either Selective Deployment or Full Deployment.
    7. Click on Retrieve Metadata.

 

6. Deployment via Version Control Revision

Please follow below steps to do a Deployment from Version Control Revision to Salesforce Org.

  1. From the AutoRABIT home page, select Deployment > New Deployment.
  2. Under Deployment Details, complete the following:
    1. Give a label name in the Deployment Label field.
    2. In Deployment From, select Version Control Revision from the drop-down list.
    3. Select a version control system, repository, branch, and the revision number from which the metadata has to be deployed.
    4. Choose a Destination Org.
    5. Go ahead with either Selective Deployment or Full Deployment.
    6. Click on Retrieve Metadata.

 

7. Deployment via Commit Label

Deploy the EZ-Commit labels to a target sandbox directly from AutoRABIT.

  1. From the menu, select Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From select Commit Label.
  4. Select a version control system, repository, and the branch from which the metadata has to be deployed.
  5. In EZ-commit label, select the label that has to be deployed
  6. Select the destination org into which the metadata has to be deployed.
  7. Go ahead with either Selective Deployment or Full Deployment.
  8. Click on Retrieve Metadata.

 

 

8. Deployment via Release Label

Create a release label and link all your commits (EZ-Commit labels) to your release and deploy the commits at once under a single Release Label. Group multiple EZ-Commit Labels as a single Release Label. The release label created can be deployed into multiple release environments from AutoRABIT.

  1. From the menu, select Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From select Release Label.
  4. Select the destination org into which the metadata has to be deployed.
  5. Go ahead with either Selective Deployment or Full Deployment.
  6. Click on Retrieve Metadata.

  • Was this article helpful?