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

[olamy]

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

Testing done

• Started Jenkins with Winstone 6.14 from this pull request on a Linux computer running Java 17
• Enabled security, registered myself as a user, and allowed logged in users to do anything
• Installed the markdown plugin and restarted Jenkins
• Installed the embeddable build status plugin and restarted Jenkins
• Installed declarative Pipeline and Pipeline plugins and restarted Jenkins
• Added an inbound agent from a Linux computer
• Defined and ran a Pipeline job
• Displayed the embeddable build status of that Pipeline job

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. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. 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).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

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 @olamy ! Could you describe any checks you performed in the "Testing done" section so that reviewers know if additional testing is needed before merge?

I've added the checks that I performed. The pull request looks very good to me.

[MarkEWaite]

Thanks again!

[NotMyFault]

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!