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

Build sub-job generation is not thread safe #53

Open
adamfarley opened this issue Dec 7, 2020 · 3 comments
Open

Build sub-job generation is not thread safe #53

adamfarley opened this issue Dec 7, 2020 · 3 comments

Comments

@adamfarley
Copy link
Contributor

What are you trying to do?

Launch multiple test jobs at the end of a build.

Expected behaviour:

These jobs should be launched in a threadsafe manner, enabling them to load the libraries they need, and for the resultant jobs to find a suitable checks publisher.

Observed behaviour:

Once we enter the multi-threaded section of openjdk_build_pipeline.groovy, we become unable to load new libraries (such as openjdk-jenkins-helper), and the test jobs it generates sometimes show this non-fatal error:

[Checks API] No suitable checks publisher found.

It's possible that both of these issues are caused by the groovy pipeline scripts being unable to generate new jobs in a threadsafe way. This issue is to cover centralized discussion over whether this is causing the problem, and ways in which it can be resolved.

@adamfarley adamfarley changed the title Test job generation (in build scripts) is not thread safe Build sub-job generation is not thread safe Dec 7, 2020
@karianna
Copy link
Contributor

@rysolv-bot
Copy link

karianna has contributed $20.00 to this issue on Rysolv.

The total bounty is now $20.00. Solve this issue on Rysolv to earn this bounty.

@karianna
Copy link
Contributor

I'm testing whether or not Rysolv interacts cleanly with GitHub issues - I've funded this one purely as an experiment and this is not an indication that the TSC has approved doing this more broadly.

@M-Davies M-Davies transferred this issue from adoptium/temurin-build Feb 18, 2021
AdamBrousseau added a commit to AdamBrousseau/ci-jenkins-pipelines that referenced this issue Mar 9, 2022
Infer vendor version from configure arguments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

4 participants