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

Enable concurrent builds on the pr-tester #2053

Closed
M-Davies opened this issue Sep 7, 2020 · 0 comments · Fixed by #2070
Closed

Enable concurrent builds on the pr-tester #2053

M-Davies opened this issue Sep 7, 2020 · 0 comments · Fixed by #2070
Assignees
Labels
enhancement Issues that enhance the code or documentation of the repo in any way jenkins Issues that enhance or fix our jenkins server regeneration Issues that provide enhancements or fixes to our jenkins job regenerators

Comments

@M-Davies
Copy link
Contributor

M-Davies commented Sep 7, 2020

Right now, concurrency is not possible for the pr-tester due to the jobs overwriting one another. As a result, pr testing takes a long time and run tests doesn't show any notification of the tests being queued (since concurrent builds are disabled) (This will be implemented as part of #2055). We need to find a way to either enable concurrency for the pr tester

@M-Davies M-Davies added enhancement Issues that enhance the code or documentation of the repo in any way jenkins Issues that enhance or fix our jenkins server regeneration Issues that provide enhancements or fixes to our jenkins job regenerators labels Sep 7, 2020
@M-Davies M-Davies self-assigned this Sep 10, 2020
@karianna karianna added this to the September 2020 milestone Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issues that enhance the code or documentation of the repo in any way jenkins Issues that enhance or fix our jenkins server regeneration Issues that provide enhancements or fixes to our jenkins job regenerators
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants