Status: Resolved (View Workflow)
Pipeline Model Definition API 1.7.1
There is a risk of binary compatibility conflict there
Require upper bound dependencies error for com.google.guava:guava:11.0.1 paths to dependency are:
com.google.guava:guava:11.0.1 (managed) <- com.google.guava:guava:13.0.1
I filed https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/401 with a speculative fix. As far as I can tell this issue should have existed for a long time; the relevant dependencies have not been updated in Declarative for years.
A fix for this issue was just released in Pipeline: Declarative plugin version 1.7.2.
FWIW, I don't see any issues with the version picked up by pipeline-model-api itself, so I think this is specific to artifacts that depend on it. Easy enough to add an exclusion to avoid the problem.