Product / Deployments & automation / Tasks

Tasks: scheduled and on-demand CI/CD pipelines

Updated November 2026 ยท Tasks docs โ†’

Run any pipeline on a schedule or on demand, with parameters: nightly builds, backups, infrastructure changes and maintenance jobs.

TL;DR

  • Schedule pipelines with cron syntax, or run them by hand.
  • Pass parameters when a task starts.
  • Each run keeps its history and logs.
  • Tasks use the same pipeline YAML as CI.

Watch: Tasks

What it does

  • Automated and on-demand tasks from one definition.
  • Parameters you fill in at start time, available as environment variables.
  • Script jobs such as database migrations or cache warm-ups.
  • Resource-heavy jobs off the main CI path, for example nightly end-to-end suites.
  • Infrastructure as code: run Terraform or similar on a schedule.
  • Execution history for every run. See tasks.

Docs for this feature

FAQ

Can a task run on a schedule?

Yes. Give the task a cron expression and it starts the pipeline on that schedule. You can also run it by hand at any time.

Can I pass values into a task?

Yes. Define parameters on the task; their values are available to the pipeline as environment variables.

Which pipeline does a task run?

Any pipeline file in your repository, on the branch you choose.

Next steps

Read the Tasks docs โ†’ ยท All Deployments & automation features โ†’ ยท Plans and pricing โ†’

Star us on GitHub