CI/CD · Build Artifacts
GitHub Actions Artifacts: Make Build-to-Release Handoffs Explicit
Pass named build outputs between jobs with explicit dependencies, clear paths and deliberate retention.
A build job produces files; a deployment job needs those exact outputs. Treat that transfer as an explicit part of the pipeline rather than assuming jobs share a working directory.
Name the handoff
Upload the build output as a named workflow artifact. In the consuming job, download that artifact by name into a deliberate directory. GitHub provides upload-artifact and download-artifact actions for this exchange.
Declare the dependency
If release depends on build output, add needs: build to the release job, where build is the producer’s job identifier. This establishes execution order; the artifact actions carry the files. Neither responsibility replaces the other.
Keep outputs distinct
Store deployable bundles separately from test reports. Descriptive names help reviewers identify the intended package, especially when a workflow produces several outputs. Avoid uploading the whole workspace, which may contain unnecessary or sensitive files.
Set retention deliberately
Use retention-days when a custom lifetime is needed, within repository and organization limits. Choose a period that supports investigation without retaining every temporary result indefinitely.
Verify consumption
Check that the download path contains the expected files before deployment. Record the producing commit and artifact identity so a release can be traced back to the build that created it.