Alternative to uploading to the same named Artifact multiple times
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
With version 2 of the toolkit or v4 of upload-artifact it is not possible to upload to the same named artifact anymore, as we are using it for some matrix jobs also the limit of 10 artifacts is an issue if I rename all artifacts to a unique name. Is there any workaround?
To Reproduce
Steps to reproduce the behavior:
Upload more artifacts to same named artifact
Expected behavior
A workaround to not exceed the limit of 10 artifacts but still upload all needed artifacts
We used the upload action to store reports and uploaded them to one artifact with subfolders for each matrix run
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reviewing the upload-artifact behavior in the toolkit v2 and upload-artifact v4 context, including matrix jobs and the ten-artifact limit; done means identifying and documenting a supported way to collect all reports without exceeding that limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100