Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] It is not clear how using the same name and overwrite: true works between workflows #668

Open
piedrahitapablo opened this issue Jan 24, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@piedrahitapablo
Copy link

What files would you like to change?

We recently migrated some repos from v3 artifact actions to v4, and everything worked, but from time to time, we started seeing some time-outs while trying to download artifacts using actions/download-artifact@v4. After trying many things, the definitive solution appears to be adding overwrite: true. I wondered how that overwrite: true works if two workflows run simultaneously using the same artifact name. I tried reading the README and the Actions Artifacts docs but didn't find any mention to this, so I'm asking here:

  • Are the workflows going to collide and overwrite each other?
  • Is it better to use a unique name per workflow? say name: build-${{ github.run_id }}?

For context, here's the upload code:

      - name: Save build folder
        uses: actions/upload-artifact@v4
        with:
          name: build
          if-no-files-found: error
          path: build.tar.gz
          retention-days: 1
          overwrite: true

and the download code:

      - name: Download the build folders
        uses: actions/download-artifact@v4
        with:
          name: build

Any help would be appreciated, thanks in advance!

What are your suggested changes?

Clarify the behavior of overwrite: true between workflows

@piedrahitapablo piedrahitapablo added the documentation Improvements or additions to documentation label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant