You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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:
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.
The text was updated successfully, but these errors were encountered: