Skip to content
Install

Run jobs and pipelines

A job runs work that finishes, such as a cleanup, an import, or a report, instead of a server that stays up. Jobs run on the same cluster as your apps, so a job can reach your apps and databases without exposing them. Each job runs one or more steps in order, on a cron schedule or when you start it.

StepRuns
Scriptbash, python, or node source that you enter
App commandA command inside the image of an existing app
Custom imageAny container image, with an optional command
  1. In the sidebar, go to Jobs.
  2. Select New job.
  3. Select the project.
  4. In Name, enter a name, such as nightly-cleanup.
  5. In Schedule, select a preset, Custom cron…, or Manual only.
  6. In If a run is still going, select Skip the new run or Run them in parallel.
  7. Add one or more steps.
  8. Select the type of each step.
  9. (Optional) Set a timeout, retries, and CPU for each step.
  10. Select Create job.

A job with a schedule runs as a Kubernetes CronJob. A job without one runs only when you start it.

Open the job and select Run now.

To pause a schedule, select Pause on the job page, or run orchard job pause <id>.

Each run has a status, a duration, and output for each step. Steps run in order, and each one has its own logs and exit code. Orchard keeps past runs on the job page. To list them from the CLI, run orchard job runs <id>.

Script steps run in a small image for the language you select.

RuntimeDefault image
bashdebian:12.15-slim
pythonpython:3.12.16-slim
nodenode:22.23.5-slim

These images leave out common tools. For example, debian:12.15-slim has no curl or wget. If a step needs a tool, use a Custom image step, or install the tool in the first line of the script.

To change a default image for the whole instance, set JOB_RUNTIME_IMAGE_BASH, JOB_RUNTIME_IMAGE_PYTHON, or JOB_RUNTIME_IMAGE_NODE on the server.

A job in the same environment as an app can reach the app by its internal address.