job output
A small string a job publishes in its outputs block so that jobs which need it can read it.
In more detail
It usually republishes a step output. Job outputs are for short values such as a version or an image tag; files cross between jobs as artifacts instead.
Example
outputs:
tag: ${{ steps.meta.outputs.tag }}Related terms
- step output — A named value a step writes as key=value to the file named by GITHUB_OUTPUT, which later steps read through the steps context.
- needs — The job key that makes a job wait until the jobs it names have finished successfully.
- artifact — A file produced by a build, such as a compiled program or an image, that is stored and passed on to later steps.
Taught in
- Workflows, Jobs, Steps, and Actions — Continuous Integration & Continuous Delivery Pipelines
- Passing Data Between Jobs: Artifacts — Continuous Integration & Continuous Delivery Pipelines
- Scaling with Matrix Builds — Continuous Integration & Continuous Delivery Pipelines
- Expressions, Contexts And The If That Is Always True — GitHub Actions (GH-200) Exam Prep
- Reusable Workflows: Inputs, Secrets And Outputs Across A Call — GitHub Actions (GH-200) Exam Prep
- Outputs, Artifacts, Caches And Job Summaries — GitHub Actions (GH-200) Exam Prep
- YAML-Reading Sprint: What Happens When This Runs? — GitHub Actions (GH-200) Exam Prep