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

[feat req] v4: add option to disable the 10 artifacts per job limit #470

Closed
database64128 opened this issue Dec 15, 2023 · 4 comments
Closed
Labels
enhancement New feature or request

Comments

@database64128
Copy link

What would you like to be added?

An option to remove the limit and restore the old behavior (before v4).

Why is this needed?

I have a workflow that needs to upload 24 artifacts in a single job. It is not possible to split the workflow into multiple jobs.

@siegfriedpammer
Copy link

Is there any documentation or explanation for why this limit was added in the first place?

@JackCoplandGranta
Copy link

Would be useful. we have a build that outputs 15 that caught us out when we tried to upgrade to v4. For anyone else in the same situation you can do a mix to take advantage of the speed gain - pick your 10 largest artifacts in that job and output them using v4, and use v3 for the others.

@robherley
Copy link
Contributor

@JackCoplandGranta @siegfriedpammer @database64128

👋 The limit has been raised to 500 Artifacts per job.

We chose to introduce a limit to avoid abuse scenarios. We did some data analysis, the 10 artifacts limit covered covered ~93% of all the workflow runs on GitHub.

We decided to raise it to 500 to avoid any friction without risk of abuse. Having 500 per job covers 99.99% of runs on GitHub.

@database64128
Copy link
Author

Thanks. 500 sounds like a reasonable limit.

markmssd added a commit to markmssd/upload-artifact that referenced this issue Jan 27, 2024
According to actions#470 (comment), the limitation has been raised from `10` to `500`. This PR simply updates the docs to reflect the change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants