Skip to main content

How workflows work

In briefA workflow is a scheduled, dependency-ordered set of jobs. Frequencies, calendars and build settings decide when its jobs are eligible; job, threshold, resource and expression dependencies decide their order; agent assignment decides where each runs; and events fire commands in response to outcomes. Workflows are versioned and deployed to environments.

WhereDesign › Workflows, where a workflow is built in the workflow editor. Its run is watched on Operations › Processes — see How the daily run works.

When

  • You are designing a workflow and need the model behind it.
  • A job did not run when, where or in the order you expected.
  • You are deciding between a specific agent and an agent pool for a job.

How

  1. Add jobs, each with a job type and an agent assignment.
  2. Give each job a frequency, with its build status and timing settings.
  3. Add the dependencies that order the jobs, and any events.
  4. Commit a version and deploy it to an environment.
Notes
  • A job dependency can wait for success, failure or any result.
  • Build Status values On Hold, Do Not Schedule, To Be Skipped and Disabled are by design; check them before treating a missing job as a fault.
  • Allow Multi-Instance builds a workflow as several named schedule instances for the same date.
Watch out
  • Exceeded Max Runtime fires while the job is still running; the job's status does not change.