Automation & protection

Release management

Scheduled deployments, drafts, environment variables, partial rollback, reports and DORA metrics.

Tools for planning releases, keeping environments apart, and reporting on what went out.

Schedule a deployment

In the deploy panel, set When to Schedule and pick a date and time (your local time, up to 60 days ahead). The button changes to Schedule deployment.

  • The job waits as Scheduled in the deploy queue, at the end of its org's lane, and on its deployment page (starts …).
  • At that time it joins the queue like any other job: queue policies, smart tests and superseding all apply.
  • If the org needs approval, the job waits for an owner or admin first, then for its time.
  • Cancel removes a scheduled job before it starts.

Draft packages

Not ready to deploy yet? In the deploy panel, click Save draft and give it a name. A draft keeps the selected components, cherry-picked changes, test choices, smart-fix choices (fixes you undid) and notes.

Find drafts under History → Drafts. Open brings back the comparison with everything selected and the deploy panel open, ready to validate or deploy. Update draft saves changes to it.

A draft remembers its comparison. If the orgs have changed since, click Re-compare first and check the package again.

Environment variables

Some values differ per environment: an integration's endpoint URL, a named credential's host, a notification email. Give each target org its values once:

  1. Connections, then Variables on the org.
  2. Add a variable: a Name, the text to Find (as it appears in your source), and what to Replace it with in this org. Optionally limit it to one metadata type.
  3. Tick Secret to hide the value after saving.

Every validation and deployment to that org replaces the text in everything it deploys. The deploy panel and the deployment log list what was replaced and where. Comparisons always show the unreplaced source.

Partial rollback

Roll back on a successful deployment now lists every component it would restore or remove (components the deployment created are removed). Untick the ones to keep as they are; the button reads Roll back 3 of 7. The rollback is labelled Partial rollback in history.

Deployment reports

Report on a deployment page opens a printable report: summary, approver, timings, tests, every component with its cherry-picks and smart fixes, environment variables, errors and the full activity log. Use Print or save as PDF for change records, or CSV for a spreadsheet.

DORA metrics

Overview shows the four DORA metrics for your production orgs over the last 30 days (or every org if you haven't connected a production org):

Metric How it's measured
Deployment frequency Successful and failed deployments per week
Lead time for changes Median time from the comparison to the change being live
Change failure rate Share of deployments that failed or were rolled back
Time to restore Median time from a failed deployment to the next successful one on that org

The badge places you in a band (elite, high, medium, low) using simplified DORA thresholds.

Something unclear or missing on this page?