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

Treat plugin dependency mismatches involving snapshots as nonfatal

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core

      Split out from a comment in JENKINS-51594: if PluginWrapper.resolvePluginDependencies detects an apparent violation of plugin dependencies due to a version comparison involving a Maven snapshot, it should treat this as a warning rather than a hard error, since this is a developer workflow and the version comparison was not necessarily accurate.

          [JENKINS-52665] Treat plugin dependency mismatches involving snapshots as nonfatal

          Jesse Glick created issue -
          Jesse Glick made changes -
          Epic Link New: JENKINS-50686 [ 189770 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-51594 [ JENKINS-51594 ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Labels Original: lts-candidate New: lts-candidate plugin-manager
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-21486 [ JENKINS-21486 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 3551 (Web Link)" [ 21208 ]
          Jesse Glick made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]

          Jesse Glick added a comment -

          Mostly relevant for making JenkinsRule-based tests pass locally; also affects interactive run, though this can be worked around:

          mvn -Dhudson.PluginWrapper.dependenciesVersionCheck.enabled=false hpi:run
          

          Jesse Glick added a comment - Mostly relevant for making JenkinsRule -based tests pass locally; also affects interactive run, though this can be worked around: mvn -Dhudson.PluginWrapper.dependenciesVersionCheck.enabled=false hpi:run
          Jesse Glick made changes -
          Description Original: Split out from a comment in JENKINS-51594: if {{PluginWrapper.resolvePluginDependencies}} detects an apparent violation of plugin dependencies due to a version comparison involving a Maven snapshot, it should treat this as a warning rather than a hard error, since this is a developer workflow and it the version comparison was not necessarily accurate. New: Split out from a comment in JENKINS-51594: if {{PluginWrapper.resolvePluginDependencies}} detects an apparent violation of plugin dependencies due to a version comparison involving a Maven snapshot, it should treat this as a warning rather than a hard error, since this is a developer workflow and the version comparison was not necessarily accurate.

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: