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

workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Jenkins informs me about security updates for workflow-{cps,job,multibranch,support} but I get a warning in the Update Center for each of them:

      Warning: This plugin requires dependent plugins be upgraded and at least one of these dependent plugins claims to use a different settings format than the installed version. Jobs using that plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.

      I checked the dependencies and as it seems, those four plugins require workflow-step-api in version 2.13, but 2.14 was released 3 months ago, according to its plugin site.

       

        Attachments

          Activity

          Hide
          abayer Andrew Bayer added a comment -

          So in practice, this isn't an issue - we don't always catch up dependencies to the newest all the time, but 99% of the time, you won't have any compatibility problems. This is especially true for something like workflow-step-api. So you can just upgrade to 2.14 without worries.

          Show
          abayer Andrew Bayer added a comment - So in practice, this isn't an issue - we don't always catch up dependencies to the newest all the time, but 99% of the time, you won't have any compatibility problems. This is especially true for something like workflow-step-api . So you can just upgrade to 2.14 without worries.
          Hide
          ctwx Christian Wansart added a comment -

          Thanks, I'll try. If it breaks try to install the old versions. I was a bit confused that the security updates of the named above plugins are newer than then its dependency causing the warning.

          Show
          ctwx Christian Wansart added a comment - Thanks, I'll try. If it breaks try to install the old versions. I was a bit confused that the security updates of the named above plugins are newer than then its dependency causing the warning.

            People

            • Assignee:
              Unassigned
              Reporter:
              ctwx Christian Wansart
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: