Revert "Update dependency org.jenkins-ci.main:jenkins-test-harness to v2505"#11125
Conversation
… v2505 (…" This reverts commit a7a7a1d.
|
An incremental build of the master branch (prior to this pull request) in the plugin BOM passed the http request plugin test. The change I made in the plugin BOM was: I ran the plugin BOM test with the command: The http request plugin test fails if I use the incremental build of the master branch and also upgrade the Jenkins test harness version in the test. The change I made in the plugin BOM for that was: I ran the plugin BOM test with the command: Unfortunately, I'm not sure what that means. Upgrading Jenkins test harness to 2505.x inside Jenkins core does not break the plugin BOM test of http request plugin, but upgrading Jenkins test harness to 2505.x in the plugin BOM does break it. I also confirmed that the http request plugin test is not broken when run with the incremental of Jenkins core inside the http request plugin repository. The changes I tested in the http request plugin repository look like this: The command I used to run those tests was: When I uncomment the upgrade to Jenkins test harness 2505.x in that change to http request plugin, then the test fails |
|
Interesting analysis, I try to take a look later this week 👀 |
|
I think that we can safely close this pull request. I've had some tutoring from @jglick that should allow me to find the change in Jetty 12.1.1 that is causing the test failure in the http request plugin. The winstone 8.14 release includes Jetty 12.1.1 and stapler release 2033.va_95221851a_23 depends on Jetty 12.1.1 . @alecharp is also exploring the use of Jetty 12.1.1 in the context of Java 25 with a draft pull request at: |
Reverts #11106
As per jenkinsci/jenkins-test-harness#1031