When a Jetty 12 Jenkins test harness is used (i.e., one built from the prototype branch of jenkins-test-harness), the following tests fail:

• io.jenkins.plugins.casc.TokenReloadCrumbExclusionTest
• io.jenkins.plugins.casc.yaml.YamlSourceTest

The tests are failing because the API has changed. The tests are just looking for a simple instance of a request, so perhaps ServletCoreRequest could be used instead—or otherwise, a Mockito-based mock, since this isn't a real integration test anyway.

Ideally a change could be found that can be delivered against the current release of Jetty 10 while also being forward compatible with Jetty 12. If not, then the PR will have to remain in draft until we release JTH with Jetty 12 support. Either way, we should prepare the PR in advance.