Skip to content

Support rerunning builds that were never started due to concurrency limits #9082

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

Closed
Cadair opened this issue Apr 6, 2022 · 3 comments
Closed

Comments

@Cadair
Copy link

Cadair commented Apr 6, 2022

This is a small extension to the fix for #6524.

It seems that you can't restart a build that didn't run due to concurrency limits:

image

(it never did retry in 5 minutes...)

@humitos
Copy link
Member

humitos commented Apr 6, 2022

Hi! It does retry every 5 minutes. However, it may happen the concurrency limit is still reached but as the message does not change it's confusing (see #9011).

If after a long time it does not retry, it may be a bug, however. Can you please fill the template of the issue, providing your project URL and the build's URL as well?

@Cadair
Copy link
Author

Cadair commented Apr 6, 2022

Hi thanks for the info!

Have updated the post with URLS. In the case where it stops retrying it would be useful if there was a retry button.

@humitos
Copy link
Member

humitos commented Apr 7, 2022

This issue is a duplicate of #9014. Please, subscribe there to receive notifications.

@humitos humitos closed this as completed Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants