Branch Deployment
Deployment pushes your branch’s metadata components into a target Salesforce org. It deploys actually applies changes, making it the final step in moving code/config into Salesforce environments.
What is Deploy
Deploy allows you to move metadata components from a Revvy branch into a connected Salesforce org.
It ensures that:
Selected branch components are applied to the target org
Optional destructive changes can remove metadata no longer needed
Apex tests and post-deployment steps run for compliance and stability
By running deployment after validation, you can confidently promote changes into higher environments like UAT and Production.
Prerequisites
A connected Salesforce org available as the deployment target.
A branch containing metadata components to deploy.
Appropriate permissions to execute deployment jobs in Revvy.
(Recommended) Validation completed successfully.
How to Run Deploy
Step 1: Open Deploy Wizard
Open the branch.
In the branch header, click the Deploy button.
The Deploy wizard appears with multiple steps.
Step 2: Select components
A list of branch components is displayed.
Choose one or more components for deployment.
Use Add all to include the entire branch.
When ready, click Next.
Step 3: Select connection
Pick the Salesforce org connection where deployment will run.
The org list shows details like org type, creator, and last retrieve date.
Once selected, click Next.
Step 4: Destructive changes
If you need to remove metadata, you can include destructive changes.
Components can be marked for Pre (delete before deploy) or Post (delete after deploy).
Add or remove items as needed, then click Next.
Step 5: Configure settings
This screen lets you fine-tune deployment:
Run tests – Choose the Apex test level:
Default – Runs only package tests
Do not run tests – Skips all tests (only for non-production orgs)
Run local tests – Runs org tests except managed packages
Run all tests – Executes every test, including managed packages
Run specified tests – Lets you pick individual classes
Deploy profile settings only for selected components – Deploys only the Profile settings that are related to the components you selected in the branch, instead of deploying the entire Profile.
Deploy permission set settings only for selected components – Deploys only the Permission Set settings tied to the selected branch components, avoiding unnecessary changes to other settings.
Run post-deploy Apex code – Executes defined Apex scripts after deployment completes.
Ignore warnings on deployment – Allows deployment to continue even with warnings.
Click Run to start deployment.
How to Check Deployment Status
Once started, the Deploy job appears under Activities → Jobs.
Status values include: Queued, In Progress, Completed, Exception.
Filters (type, status, date range) help you quickly find deployment jobs.
How to view deployment results and logs
From Activities → Jobs, click the completed Deploy job entry.
The results page shows:
Connection used
Status, duration, start/end time
Who triggered the deployment
Logs on the right display details such as:
Backup creation (before deployment begins)
Manifest preparation
Deployment steps and Apex test execution
Number of deployed components
If the deployment fails or encounters errors, detailed messages appear in the logs.
Use Refresh to live-update logs during deployment.
Rollback
On the deployment results page, a Rollback button is available if a backup was created.
Clicking Rollback restores the org to its pre-deployment state using the backup snapshot.
Best Practices
Always validate before deploying into UAT or Production.
Use Pre and Post destructive changes carefully; confirm items are safe to delete.
In lower environments, you can use Do not run tests for speed; in Production, always use Run all tests or Run local tests.
Use Profile/Permission Set scoping to avoid unnecessary overwrites.
Review logs carefully after deployment to confirm success.
Leverage Rollback immediately if unexpected issues occur.
Document each deployment with clear commit messages for auditing.
Last updated
Was this helpful?