Skip to main content
SerpentHelp Center
Back to Serpent homepageBack
EN
EnglishENNederlandsNLالعربيةARFrançaisFRDeutschDE
Start free

Deploying Changes

Push a Work Item's changes to a target org through a guided, resumable flow that validates before anything lands.

Updated August 20, 2026 · 1 min read

Try it in Serpent

Deploying pushes the Salesforce metadata on a Work Item into a target org. Serpent guides you through it as a stepped, resumable flow and validates the change before anything lands, so a deployment is not an all-or-nothing leap.

The four steps

  1. Configure

    Pick the target org or scratch org. The branch is the Work Item's branch, so there is nothing to wire up by hand.

  2. Select files

    Choose the components to deploy. Serpent scopes to just what changed, so you are not shipping the whole org.

  3. Validate

    Run a dry-run validation against the target. A clean result continues automatically; failures stop here so you can fix them first.

  4. Deploy

    Deploy the validated change and watch the progress and result.

Only what changed

By default Serpent deploys a delta - only the components the Work Item touched - rather than the entire source tree. This keeps deployments fast and their blast radius small.

Validate before you deploy

The dry-run step checks the change against the real target org before it lands, so missing dependencies and test failures surface as a validation result, not a broken org. To deploy straight between two orgs without a Work Item, see Org-to-Org Deployment.