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

Upgrade Winstone from 6.14 to 6.16 (upgrade Jetty from 10.0.17 to 10.0.18)

    • 2.431, 2.426.3

      Problem

      Jenkins core ships an outdated release of Jetty (at the time of this writing, 10.0.17).

      Solution

      Upgrade Jetty from its current release to the latest release (at the time of this writing, 10.0.18).

      Success criteria

      The success criteria for this ticket are as follows:

      • Winstone released with the latest version of Jetty (at the time of this writing, 10.0.18)
      • Stapler released with the latest version of Jetty (at the time of this writing, 10.0.18)
      • Jenkins Test Harness (JTH) released with the latest version of Jetty (at the time of this writing, 10.0.18)
      • Maven HPI Plugin released with the latest version of Jetty (at the time of this writing, 10.0.18)
      • Plugin parent POM upgraded to the abovementioned releases of Jenkins Test Harness (JTH) and Maven HPI Plugin
      • Jenkins core upgraded to the abovementioned release of Winstone
      • jetty-maven-plugin in core upgraded to the same version of Jetty as the abovementioned release of Winstone
      • Weekly release shipped with all of the above changes

          [JENKINS-72266] Upgrade Winstone from 6.14 to 6.16 (upgrade Jetty from 10.0.17 to 10.0.18)

          Basil Crow added a comment -

          Proposing the Jenkins core changes as a (weak) backport request for 2.426.2. Reasoning: for as long as I can remember, about half of the time that we upgrade Winstone, users end up wanting a backport, and they often don't know how to request a backport, or we forget to actually do the backport. So this ticket is an attempt to be more proactive. I don't feel strongly about it, so if this backport request is rejected then that is quite alright.

          Basil Crow added a comment - Proposing the Jenkins core changes as a (weak) backport request for 2.426.2. Reasoning: for as long as I can remember, about half of the time that we upgrade Winstone, users end up wanting a backport, and they often don't know how to request a backport, or we forget to actually do the backport. So this ticket is an attempt to be more proactive. I don't feel strongly about it, so if this backport request is rejected then that is quite alright.

            basil Basil Crow
            basil Basil Crow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: