[CBI] Failing CI builds for Epsilon
Summary
Our CI builds have started failing today. We think it may be due to missing the "Lockable Resources" plugin that provides the lock
method to our Jenkinsfile
.
Steps to reproduce
To reproduce it, you can run a CI build from the Epsilon JIPP.
What is the current bug behavior?
Here is a failed build:
https://ci.eclipse.org/epsilon/job/interim-kubernetes/job/main/116/
The build fails with:
Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: d556f488-8df9-43af-887b-f26a2632d7d3
java.lang.NoSuchMethodError: No such DSL method 'lock' found among steps [...]
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:219)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:124)
...
Finished: FAILURE
What is the expected correct behavior?
The CI build should work as usual. You can see from the build log that the Maven build went well, and the last time we ran that stage on January 22nd, it also worked well:
https://ci.eclipse.org/epsilon/job/interim-kubernetes/job/main/114/
Relevant logs and/or screenshots
Please see the error message in the above log.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
We are unable to release any interim versions until this is fixed. We also want to release the 2.5.0 stable version soon.