You are here:
Deploy a Change Set
You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
- From Setup, enter Inbound Change Sets in the Quick Find box, then select Inbound Change Sets.
-
Click Deploy next to the change set you want to deploy.
If you prefer to review the change set before deploying it, first click the name of the change set to view its detail page. When ready, click Deploy.
If the change set has been deleted from its source org, the Deploy link isn’t available. If a deployment of the change set is already in progress, the Deploy link isn’t available until after the deployment completes.
Alternatively, you can perform a quick deployment to shorten your deployment time to production. Change sets that have been successfully validated can sometimes qualify for a quick deployment. For more information, see Quick Deployments.
To prevent a deployment from failing when components are referenced by Apex jobs, in the Deployment Settings page, click Allow deployments of components when corresponding Apex jobs are pending or in progress, and then click Save. This option lets you deploy components that are referenced by Apex jobs—including scheduled jobs, batch jobs, and future methods— that are pending or in progress. This option applies to change sets and deployments that are started through the Metadata API.
A change set is deployed in a single transaction. If the deployment is unable to complete for any reason, the entire transaction is rolled back. After a deployment completes successfully, all changes are committed to your org and the deployment can’t be rolled back.
The Lightning Platform requires that at least 75% of your code is covered by unit tests before you can deploy it to a production org. Ideally, strive for 100% coverage. The code coverage restriction isn’t enforced for sandbox or Developer Edition orgs.
- Enabling this option can sometimes cause Apex jobs to fail due to unsupported changes.
- This option doesn’t affect editing and saving Apex code in the Salesforce user interface (in Setup or the Developer Console). These operations fail when there are active jobs associated with the Apex class.
