Skip to main content
AutoRABIT, Inc.

New Deployment

New Deployment

The deployment process enables you to safely transfer a wide variety of new developments – be it validation rules, custom objects, new fields or apex code or a huge range of other components – from your sandbox to the production instance.

 

Different Deployment Methods

There are various methods to carry out the deployment in AutoRABIT:

  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
  9. Validate and Commit Label
  10. Previous Deployment Labels

 

1. Deployment via Salesforce Org

You can automate the deployment of the latest changes done in your source sandbox into a destination Sandbox.

For Sandbox to Sandbox deployments:

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From select Salesforce Org.

1.png

  1. Metadata Types, you can choose to deploy either the entire Org or only Full Profiles and Permission sets.
a) Full Profiles: Full Profiles will fetch all the profiles available in selected Salesforce Orgs.
b) 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. Select Source and Destination Org.
  2. Choose between Selective and Full Deployment.

 

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. Metadata Filter. You can fill the remaining field under Metadata Filter or you can simply ignore. It is optional.
  3. At the bottom of the page, click on either of the option:
    1. Pre-Destructive changes: Pre-Destructive changes allows users to remove the selected members from your destination and proceed with deployment.
    2. Post-Destructive changes: Post-Destructive changes allows users to remove the selected members from your destination post when the deployment is completed successfully.
    3. Retrieve Metadata. It will retrieve all the metadata types and its members to be deployed to the destination org.
  4. Click on Retrieve Metadata option opens a new page and displays the deployment information on the left side and list of all intended metadata on the right side of the screen.

2.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. Next choose either Deploy or Compare Orgs & Deploy.
    1. Deploy: Directly deploy to the destination Org.
    2. Compare Orgs & Deploy provide you an option to validate the deployment; to check if the deployment would be successful or not.
  3. Compare Orgs & Deploy. Once a list of all the metadata members is displayed, select the members that you want to deploy and click Compare Orgs & Deploy. The metadata is fetched from the destination and the metadata differences are displayed.

3.jpg

  1. Click on a log to see the difference report of a metadata member.

4.png

  1. Deploy. Once a list of all the metadata members is displayed, select the members that you want to deploy and click Deploy.
  2. On the next screen, you need to choose the required filters.

5.png

  1. 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 the metadata types.
  2. Validate only: The label is validated and saved without being deployed. It is saved and can later be used in Quick Deploy.
  3. 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 to the original metadata.
  4. 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.

11. 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: Build is deployed without running any test cases.
  2. Run All Tests in Org: All tests are run. The tests include all tests in your organization, including tests of managed packages.
  3. Run Local Tests: All 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.
  4. Run Specified Tests: This option allows the user to run specific Apex test classes post deployment.

6.png

  1. At last, click on the Deploy option. It will redirect to the Deployment History screen where you can find the deployment process being carried out.

 

Full Deployment

Full Deployment 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.

 

2. Deployment via AutoRABIT Build

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

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select AutoRABIT Build from the drop-down list.
  4. Choose Project Name and Build No from the drop-down list.
  5. Select a Destination Org.
  6. In Deployment Type, choose either Selective Deployment or Full Deployment.
  7. Click on Retrieve Metadata.

7.png

 

 

3. 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. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Package.xml from the drop-down list.
  4. In the succeeding pop-up, upload a package.xml file.

8.png

  1. Metadata Types, you can choose to deploy either the entire Org or only Full Profiles and Permission sets.
a) Full Profiles: Full Profiles will fetch all the profiles available in selected Salesforce Orgs.
b) 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 a Source and Destination org.
  2. Go ahead with either Selective Deployment or Full Deployment.

9.png

 

4. Metadata Zip

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

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. .In Deployment Label, give a label name.
  3. In Deployment From, select Metadata Zip from the drop-down list.
  4. In the succeeding pop-up, upload a zip file.

10.png

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

11.png

  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. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Version Control from the drop-down list.
  4. Select a Version ControlRepository, and the Branch from which the metadata has to be deployed.
  5. Metadata Types, you can choose to deploy either the entire Org or only Full Profiles and Permission sets.
a) Full Profiles: Full Profiles will fetch all the profiles available in selected Salesforce Orgs.
b) 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 a Destination org.
  2. Go ahead with either Selective Deployment or Full Deployment.
  3. Click on Retrieve Metadata.

12.png

 

6. Version Control Revision

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Version Control Revision from the drop-down list.
  4. Select a Version ControlRepository, Branch and the Revision Number from which the metadata must be deployed.
  5. Choose a Destination org.
  6. Go ahead with either Selective Deployment or Full Deployment.
  7. Click on Retrieve Metadata.

13.png

 

7. Commit Label

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

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Commit Label from the drop-down list.
  4. Select a Version Control System, Repository, and the Branch from which the metadata must be deployed.
  5. In EZ-commit label field, select the label that you wish to deploy.
  6. Choose a Destination org into which the metadata must be deployed.
  7. Go ahead with either Selective Deployment or Full Deployment.
  8. Click on Retrieve Metadata.

14.png

 

8. 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. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Release Label from the drop-down list.
  4. Choose a Destination org into which the metadata must be deployed.
  5. Go ahead with either Selective Deployment or Full Deployment.
  6. Click on Retrieve Metadata.

15.png

 

9. Deployment via Validate and Commit Label

Validates and deploy the EZ-commit labels to a target sandbox directly from AutoRABIT.

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Validate and Commit Label from the drop-down list.
  4. Choose a Source and Destination org into which the metadata must be deployed.
  5. Go ahead with either Selective Deployment or Full Deployment.
  6. Click on Retrieve Metadata.

16.png

 

10. Deployment via Previous Deployment Label

Previous Deployment Labels allows you to choose a previously deployed label and deploy it again into a new Destination (Sandbox, Org, etc.).

  1. In AutoRABIT homepage, navigate to Deployment > New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From, select Previous Deployment Label from the drop-down list.
  4. Select Source and Destination Org.
  5. Go ahead with either Selective Deployment or Full Deployment.
  6. Click on Retrieve Metadata.

17.png

 

  • Was this article helpful?