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

Feature request: sleep between concurrent groups #481

Open
1 of 2 tasks
nwsparks opened this issue May 23, 2024 · 3 comments
Open
1 of 2 tasks

Feature request: sleep between concurrent groups #481

nwsparks opened this issue May 23, 2024 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@nwsparks
Copy link

The feature request

A flag to sleep for X seconds between concurrent groups or between pr's would be very helpful to prevent build storms.

For example if concurrency was 5, you could set --second-between-executions 60 and it would process 5 repositories, wait 60 seconds, then process another 5 repositories.

Alternatively it could be done in between each PR but I suspect that is harder to accomplish. Controlling it via concurrency seems fine to me.

Implementation

  • I would like to contribute this feature if it's a suitable addition to multi-gitter
  • I have no intention of adding this feature myself.
@nwsparks nwsparks added the enhancement New feature or request label May 23, 2024
@lindell
Copy link
Owner

lindell commented May 23, 2024

Cloud you please add context on why you want to do it. And which platform you are using /GitHub/GitLab etc.

@nwsparks
Copy link
Author

sure, the platform is github. i'm doing a simple change, updating .dockerignore, which is a fast operation. I'm doing it against quite a few repositories so without a pause between pull requests it will cause a build storm and clog up CI for quite awhile.

I settled for just adding a sleep at the end of the script and low concurrency which I guess is what most people could do in lieu of a flag to control it.

@lindell
Copy link
Owner

lindell commented May 23, 2024

Seems like a valid usecase. But since it has a simple workaround I will not prioritize it. If anyone else wants to pick it up, feel free.

I think the easiest option would be to add X seconds before starting any new run (except the first batch).

@lindell lindell added the good first issue Good for newcomers label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants