Latest Version Number Format Change Breaks Container Plugin Upgrades

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor
    • Component/s: _unsorted
    • Environment:
      Jenkins 2.397 running in a container with plugins installed/upgraded in the container using the PLUGINS_FORCE_UPGRADE=true setting.

      The most recent update includes a new version number format which breaks plugin upgrades when running Jenkins in a container using the official Jenkins image.  Plugin upgrades are logged to the $JENKINS_HOME/copy_reference_file.log file.  When reviewing this log the following message was present:

      SKIPPED plugins/role-strategy.jpi : Image version (587.588.v850a_20a_30162) is older than installed version (587.v2872c41fa_e51)

      I suspect this will be a temporary issue and that as long as the next version uses the same format, it should upgrade as expected.  However, as the current version fixes a vulnerability and it was a bit of a struggle to get it installed, I thought it worth reporting.

            Assignee:
            Oleg Nenashev
            Reporter:
            Dan
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: