Skip to main content

Version and deploy a workflow

In briefCommitting a change to a workflow creates a new, numbered version; running it in an environment is a separate step, deployment. Each environment's deployment either follows Latest or is pinned to one version, so you can test a change in one environment while another keeps running the version you trust.

Notes
  • Your edits are a draft kept in this browser until you commit a version with the filled save action, Commit changes to a version. The version selector shows where you stand.
  • Renaming a workflow does not create a version.
  • To roll an environment back, edit its deployment and pin it to the earlier version. There is no separate rollback action.
  • A deployment can be limited to a window with an Effective Date and an Expiration Date.
  • Replace schedules a new deployment to take over on a future date; the current one keeps building until then.
Watch out
  • The commit action stays greyed out while any job in the workflow cannot run, including one you did not touch. Hover it to see the first problem.
  • A workflow with a Workflow Container job cannot be deployed where its sub-workflow is not deployed, or for dates the sub-workflow's deployment does not cover. Deploy the sub-workflow first.
  • A commit that changes which sub-workflows a workflow embeds is refused while the workflow is deployed as Latest somewhere those sub-workflows are not deployed.