Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63123

Pipeline Model Definition API 1.7.1 includes higher version of Guava than Jenkins

    XMLWordPrintable

Details

    • pipeline-model-definition 1.7.2

    Description

      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:
      +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
      +-org.jenkins-ci.main:jenkins-core:2.235.2
      +-com.google.guava:guava:11.0.1
      and
      +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
      +-org.jenkins-ci.main:jenkins-core:2.235.2
      +-org.kohsuke.stapler:stapler-jrebel:1.259
      +-org.kohsuke.stapler:stapler:1.259
      +-com.google.guava:guava:11.0.1
      and
      +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
      +-io.jenkins.plugins:pipeline-as-yaml:0.10-rc-SNAPSHOT
      +-org.jenkinsci.plugins:pipeline-model-definition:1.7.1
      +-org.jenkinsci.plugins:pipeline-model-api:1.7.1
      +-com.github.fge:json-schema-validator:2.0.4
      +-com.github.fge:json-schema-core:1.0.4
      +com.google.guava:guava:11.0.1 (managed) <- com.google.guava:guava:13.0.1

      Attachments

        Activity

          oleg_nenashev Oleg Nenashev created issue -
          oleg_nenashev Oleg Nenashev made changes -
          Field Original Value New Value
          Priority Minor [ 4 ] Major [ 3 ]
          oleg_nenashev Oleg Nenashev made changes -
          Summary Pipeline Model Definition API includes higher version of Guava than Jenkins Pipeline Model Definition API 1.7.1 includes higher version of Guava than Jenkins
          oleg_nenashev Oleg Nenashev made changes -
          Description Require upper bound dependencies error for com.google.guava:guava:11.0.1 paths to dependency are:
          +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-org.jenkins-ci.main:jenkins-core:2.235.2
           +-com.google.guava:guava:11.0.1
          and
          +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-org.jenkins-ci.main:jenkins-core:2.235.2
           +-org.kohsuke.stapler:stapler-jrebel:1.259
           +-org.kohsuke.stapler:stapler:1.259
           +-com.google.guava:guava:11.0.1
          and
          +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-io.jenkins.plugins:pipeline-as-yaml:0.10-rc-SNAPSHOT
           +-org.jenkinsci.plugins:pipeline-model-definition:1.7.1
           +-org.jenkinsci.plugins:pipeline-model-api:1.7.1
           +-com.github.fge:json-schema-validator:2.0.4
           +-com.github.fge:json-schema-core:1.0.4
           +-com.google.guava:guava:11.0.1 (managed) <-- com.google.guava:guava:13.0.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:
           +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-org.jenkins-ci.main:jenkins-core:2.235.2
           +-com.google.guava:guava:11.0.1
           and
           +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-org.jenkins-ci.main:jenkins-core:2.235.2
           +-org.kohsuke.stapler:stapler-jrebel:1.259
           +-org.kohsuke.stapler:stapler:1.259
           +-com.google.guava:guava:11.0.1
           and
           +-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
           +-io.jenkins.plugins:pipeline-as-yaml:0.10-rc-SNAPSHOT
           +-org.jenkinsci.plugins:pipeline-model-definition:1.7.1
           +-org.jenkinsci.plugins:pipeline-model-api:1.7.1
           +-com.github.fge:json-schema-validator:2.0.4
           +-com.github.fge:json-schema-core:1.0.4
           +-com.google.guava:guava:11.0.1 (managed) <-- com.google.guava:guava:13.0.1
          Environment Pipeline Model Definition API 1.7.1
          Jenkins 2.235.2
          dnusbaum Devin Nusbaum added a comment -

          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.

          org.jenkinsci.plugins:pipeline-model-api:hpi:1.7.2-SNAPSHOT
          ...
          [INFO] +- com.github.fge:json-schema-validator:jar:2.0.4:compile
          [INFO] |  +- com.github.fge:json-schema-core:jar:1.0.4:compile
          [INFO] |  |  \- org.mozilla:rhino:jar:1.7R4:compile
          [INFO] |  +- javax.mail:mailapi:jar:1.4.3:compile
          [INFO] |  +- joda-time:joda-time:jar:2.1:compile
          [INFO] |  \- com.googlecode.libphonenumber:libphonenumber:jar:5.3:compile
          ...
          [INFO] +- org.jenkins-ci.main:jenkins-core:jar:2.176.4:provided
          [INFO] |  +- ...
          [INFO] |  +- com.google.guava:guava:jar:11.0.1:compile
          ...

           

          dnusbaum Devin Nusbaum added a comment - 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. org.jenkinsci.plugins:pipeline-model-api:hpi:1.7.2-SNAPSHOT ... [INFO] +- com.github.fge:json-schema-validator:jar:2.0.4:compile [INFO] |  +- com.github.fge:json-schema-core:jar:1.0.4:compile [INFO] |  |  \- org.mozilla:rhino:jar:1.7R4:compile [INFO] |  +- javax.mail:mailapi:jar:1.4.3:compile [INFO] |  +- joda-time:joda-time:jar:2.1:compile [INFO] |  \- com.googlecode.libphonenumber:libphonenumber:jar:5.3:compile ... [INFO] +- org.jenkins-ci.main:jenkins-core:jar:2.176.4:provided [INFO] |  +- ... [INFO] |  +- com.google.guava:guava:jar:11.0.1:compile ...  
          dnusbaum Devin Nusbaum added a comment -

          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.

          dnusbaum Devin Nusbaum added a comment - 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.
          dnusbaum Devin Nusbaum made changes -
          Remote Link This issue links to "jenkinsci/pipeline-model-definition-plugin#401 (Web Link)" [ 25332 ]
          jglick Jesse Glick made changes -
          Component/s pipeline [ 21692 ]
          jglick Jesse Glick made changes -
          Assignee Devin Nusbaum [ dnusbaum ]
          jglick Jesse Glick made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          jglick Jesse Glick made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          dnusbaum Devin Nusbaum added a comment -

          A fix for this issue was just released in Pipeline: Declarative plugin version 1.7.2.

          dnusbaum Devin Nusbaum added a comment - A fix for this issue was just released in Pipeline: Declarative plugin version 1.7.2.
          dnusbaum Devin Nusbaum made changes -
          Released As pipeline-model-definition 1.7.2
          Resolution Fixed [ 1 ]
          Status In Review [ 10005 ] Resolved [ 5 ]

          People

            dnusbaum Devin Nusbaum
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: