CI Job Rollback
The Rollback feature enables you to revert a deployment if issues are detected post-deployment or if unintended changes were introduced.
How to Roll Back a Deployment
This section explains how to roll back a deployment in your CI jobs. The goal is to restore a previous release or deployment state.
Prerequisites
- The Rollback checkbox must be selected when creating the CI job. 
Steps
- Navigate to the CI Job Results screen. 
- Select the deployment label you want to roll back. 
- Click the Rollback icon:   
- Under API Supported > Constructive Changes, you’ll see the list of metadata components from the original deployment. All are selected by default.   
- In Choose your Pre/Post Destructive Changes, you can mark metadata present in the destination but absent in the source for deletion. These deletions are logged in the Rollback Iteration Log.  
- Choose a method for destructive changes: - Post Destructive Changes: Deletes components after deployment. 
- Pre-Destructive Changes: Deletes components before deployment starts. 
 
- The API Un-Supported section lists metadata types unsupported by the API. You can manually include these as pre or post-destructive changes.  
Additional Deployment Options
Available configuration options before rollback:
- Validate Only: Run a dry-run validation without performing the actual rollback. 
- Deploy Purge on Delete: Permanently deletes components instead of moving them to the Salesforce Recycle Bin. 
- Ignore Warnings: Continues rollback even if warnings are encountered. 

Apex Test Level
Select an Apex Test Level to validate your rollback deployment.
- For details, see Apex Unit Tests. 

Final Step
- Click Rollback to initiate the process. 
- Once completed, the rollback appears in the CI Job Results screen, tagged accordingly. From there, you can: 
- View rollback reports 
- Download the rollback package 
- Re-deploy the rollback if needed 
Last updated
Was this helpful?

