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

[CI] Prevent develop CI from running concurrently (latest build should abort any preceding build) #2747

Closed
brian-mulier-p opened this issue Dec 20, 2023 · 1 comment · Fixed by #2766
Assignees
Labels
bug Something isn't working
Milestone

Comments

@brian-mulier-p
Copy link
Member

Explain the bug

See https://docs.github.com/en/actions/using-jobs/using-concurrency
If we don't do that, we're openned to issues like triggering two builds (two merge), if the last-merged-PR-triggered build is faster, it will result in the previous build being the one pushed last and would not include the very last PR

Environment Information

  • Kestra Version:
  • Operating System and Java Version (if not using Kestra Docker image):
@brian-mulier-p brian-mulier-p added the bug Something isn't working label Dec 20, 2023
@anna-geller anna-geller added this to the v0.14.0 milestone Dec 20, 2023
@Skraye Skraye self-assigned this Dec 26, 2023
@Skraye
Copy link
Member

Skraye commented Dec 26, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants