[JENKINS-72156] Backport Upgrade to Winstone 6.14 which contains an upgrade to Jetty 10.0.17

[olamy]

Signed-off-by: Olivier Lamy [email protected]

A backport of

• [JENKINS-72156] Upgrade to Winstone 6.14 which contains an upgrade to Jetty 10.0.17 #8587

Testing done

• Started Jenkins with Winstone 6.14 from this pull request on a Linux computer running Java 17
• Confirmed the markdown plugin worked as expected
• Confirmed the embeddable build status plugin worked as expected
• Confirmed that declarative Pipeline ran as expected on an inbound agent

Proposed changelog entries

• Upgrade to Winstone 6.14 which contains an upgrade to Jetty 10.0.17

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
4. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
5. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
6. For dependency updates, there are links to external changelogs and, if possible, full differentials.
7. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[MarkEWaite]

Thanks very much! Approved

@kmartens27 this will need to be mentioned in the 2.414.3 changelog once it is merged to the stable-2.414 branch

@krisstern I think this is a good backport to have because Jetty 10.0.17 includes a fix for CVE-2023-44487

[krisstern]

@MarkEWaite Sure, let me backport this as well before the actual release

[MarkEWaite]

@MarkEWaite Sure, let me backport this as well before the actual release

Thanks, but this is already a backporting pull request. No need for an additional pull request.

[MarkEWaite]

@olamy I've not been able to isolate the cause of the test failures on the stable-2.414 branch. Any insights you can offer on what might be causing the test failures? We really want / need this in the 2.414.3 LTS but I hesitate to merge with test failures.