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

When updating a plugin, verify that dependencies exist in specified versions on UC

    Details

    • Similar Issues:

      Description

      and update them as well if necessary.

      If optional dependencies are present and they need to be updated, too.

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          I think Plugin Manager already does this normally, but might fail to do so if the new version of the dependency is not yet available. Should treat that as an error condition and forbid the original plugin from being updated.

          Show
          jglick Jesse Glick added a comment - I think Plugin Manager already does this normally, but might fail to do so if the new version of the dependency is not yet available. Should treat that as an error condition and forbid the original plugin from being updated.
          Hide
          rsandell rsandell added a comment -

          A similar problem is also when a dependency has a core version newer than the one you are using. The Plugin Manager will always download the latest version of a dependency even though its not compatible with your core version.

          Show
          rsandell rsandell added a comment - A similar problem is also when a dependency has a core version newer than the one you are using. The Plugin Manager will always download the latest version of a dependency even though its not compatible with your core version.
          Hide
          jglick Jesse Glick added a comment -

          @rsandell: true but at least in that case there is a warning displayed in the updates screen. And since the standard Jenkins update center does not serve different content according to the version query parameter, it will be quite common for the latest version of a plugin to be newer than your current core, and you would have no way to get any update of the plugin, even if there are intermediate versions which are compatible with your core.

          Show
          jglick Jesse Glick added a comment - @rsandell: true but at least in that case there is a warning displayed in the updates screen. And since the standard Jenkins update center does not serve different content according to the version query parameter, it will be quite common for the latest version of a plugin to be newer than your current core, and you would have no way to get any update of the plugin, even if there are intermediate versions which are compatible with your core.
          Hide
          danielbeck Daniel Beck added a comment -

          This already happens, so what is this issue for?

          Show
          danielbeck Daniel Beck added a comment - This already happens, so what is this issue for?
          Hide
          jglick Jesse Glick added a comment -

          See my first comment: if the dependency update is missing, Jenkins silently ignores it.

          Show
          jglick Jesse Glick added a comment - See my first comment: if the dependency update is missing, Jenkins silently ignores it.
          Hide
          danielbeck Daniel Beck added a comment -

          Right. Should be fairly rare at least.

          Show
          danielbeck Daniel Beck added a comment - Right. Should be fairly rare at least.

            People

            • Assignee:
              Unassigned
              Reporter:
              kohsuke Kohsuke Kawaguchi
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: