Skip to main content
AutoRABIT, Inc.

New Deployment

 

Deploying from one Salesforce org to another and deployments to various release environments like QA, UAT, or staging is always challenging, time consuming, and requires lot of manual effort.
AutoRABIT’s 1-click deployment enables the deployment of a build containing a set of metadata changes into various release environments either completely or selectively and also allows you to choose your own source for deployment.
AutoRABIT also supports Parallel Deployments, where multiple deployments can run at the same time without queuing.
Following are the available Source types for your deployments to Salesforce Org:              

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

Salesforce Org Deployment

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

For Sandbox to Sandbox deployments:

  1. Click New Deployment.
  2. In Deployment Label, give a label name.
  3. In Deployment From select Salesforce Org
  4. Metadata Types, you can choose to deploy either the entire Org or only Full Profiles and Permission sets.

    The list of metadata members of full profiles and full permission sets are:

    • Apex classes
    • Apps
    • Custom field permissions
    • Custom object permissions
    • Custom tab settings
    • External data sources
    • Record types
    • Visualforce pages
  5. Select a Source and Destination Orgs 
  6. 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. Use the Search filter to find intended metadata.
  3. In Previous Label, you can choose a previously deployed label and deploy it again into a new Destination (Sandbox, Org, etc.).
    • In Previous Label, select the version control label from which you want to deploy the metadata. You can choose Labels with Same source or All Labels.
    • Based on the option selected, the tab is populated with the related labels.
  4. The metadata types are displayed.
  5. You can also click and drag the mouse pointer over metadata members for selecting multiple check boxes.
  6. Click Fetch Metadata Members (bulk) to select multiple metadata types and fetch all the related members.
  7. Here you have an option to Validate the deployment to check if the deployment would be successful or not.
  8. Once a list of all the metadata members is displayed, select the members that you want to deploy and click Compare Orgs & Deploy.
  9. The metadata is fetched from the destination and the metadata differences are displayed.
  10. Click on a log to see the diff report of a metadata member.
  11. Select the metadata members/ types to be deployed.
  12. Click Deploy and choose the required filters and test levels.
    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.
     
  13. Select a Test Level: In Test Level, you can select a test type to run after a deployment has been successful. Select the level of testing from the 4 options:
     
    • No Test Run - Build is deployed without running any test cases.                                                                                                                                                                            
       

       

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

       

    • 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.      
       
       
       

       

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

  14. Click OK.
  15. Deployment summary is displayed, which contains a list of all the metadata types and members that are being deployed.
  16. Click Deploy
     
    .

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.

Deployment using AutoRABIT Build

You can deploy the AutoRABIT builds of a project.

For build based deployments:

  1. Click New Deployment
  2. In Deployment Label, give a label name.
  3. In Deployment From select AutoRABIT Build.
  4. Now choose a project and the build that has to be deployed.
  5. Choose a destination org.
  6. Go ahead with either Selective or Full deployment.

Deployments using package.xml files

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.

For deployments by using Package.xml files:

  1. Click New Deployment
  2. In Deployment Label, give a label name.
  3. In Deployment From select Package.xml.
  4. In the succeeding pop-up, upload a package.xml file
     
  5. In Metadata Types(s), choose the metadata you want to deploy.
     

  6. Choose a Source and Destination org.
  7. Go ahead with either Selective or Full deployment.

Deployments using Version Control Revision

You have an option to deploy the metadata using the version control revision number.

For deploying using the Version Control Revision Number:

  1. Click New Deployment
  2. In Deployment Label, give a label name.
  3. In Deployment From select Version Control Revision.
     
  4. Select a version control system, repository, branch, and the revision number from which the metadata has to be deployed.
  5. Choose a Destination Org.
  6. Go ahead with either Selective or Full deployment.

Deployment using EZ-Commit Label

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

For deploying using the EZ-Commit Label:

  1. Click New Deployment
  2. In Deployment Label, give a label name.
  3. In Deployment From select EZ-commit label
  4. In EZ-commit label, select the label that has to be deployed
  5. Select the destination org into which the metadata has to be deployed.
  6. Go ahead with either Selective or Full deployment.
     

Deployments using Release Labels

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

For deploying using the EZ-Commit Label:

  1. Click New Deployment
  2. In Deployment Label, give a label name.
  3. In Deployment From select EZ-commit release
  4. Select a release label and destination org.
  5. Go ahead with either Selective or Full deployment.
     

  • Was this article helpful?