Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
jenkins 2.46, ubuntu 12.04 LTS, openjdk-7
Description
Updating the pipeline-model-definition plugin to v1.2 not only beaks the running jobs, as advertised, but also all pipelines, as introduces a dependency with java 8. This java version is only required for jenkins v2.73, but for the plugin only v2.7 is needed.
I attach a simple pipeline that produces the error, and the error itself.
I see in the changelog some problems with compiling the plugin with the wrong java version, so I suspect this may be the same case.
Attachments
Issue Links
- links to
Activity
Seems to specifically be a problem with this line in MappedClosure - something weird about how Groovy compiles down @Delegate for a Map with Java 8 (even when targeting Java 7) results in too much magic with Function.class and friends getting involved. I think I've got a fix, but I need to test it more.
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
Pretty sure I nailed it with https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/205 - no more references to java.util.function.Function in the bytecode. Still need to do a Java 7 manual test at some point before releasing, though.
| Remote Link | This issue links to "PR #205 (Web Link)" [ 17816 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Auuuuuugh. Yeah, I see the problem - bumping to maven-hpi-plugin version 2.0 (with the plugin parent POM update to 2.35) means we have to use JDK8 to compile Declarative now...which should be fine, you'd think, since we're still targeting Java 7. But nope, for some reason, that damned java.util.function.Function class ends up getting referenced somewhere. Grrrr. Let me try to find a solution.