2. Advanced: Downloading from Different Workflows or Repositories
jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Create a file run: echo "Hello world" > output.txt - name: Upload result uses: actions/upload-artifact@v4 with: name: my-artifact path: output.txt deploy: needs: build runs-on: ubuntu-latest steps: - name: Download result uses: actions/download-artifact@v4 with: name: my-artifact path: download-dir - run: cat download-dir/output.txt Use code with caution.
Use v4 or later for improved performance and features like non-zipped downloads. github actions download workflow artifact
The most common scenario is downloading an artifact in a subsequent job within the same workflow run. This requires the actions/download-artifact action.
Recent updates to actions/download-artifact (v4+) allow you to download artifacts from separate workflow runs or even different repositories by providing specific identifiers. The most common scenario is downloading an artifact
The job downloading the artifact must have a needs dependency on the job that uploaded it to ensure proper sequencing.
In GitHub Actions, artifacts are the mechanism used to persist files after a job finishes and share data between different jobs or even different workflows. Whether you are passing a build binary to a deployment step or retrieving logs for debugging, understanding how to is essential for effective CI/CD. 1. Basic Usage: Downloading in the Same Workflow The job downloading the artifact must have a
Downloading artifact from different workflow #106300 - GitHub