-
Task
-
Resolution: Fixed
-
Major
-
None
When a Jetty 12 EE 9 core (i.e., one built from the jakarta branch of jenkins) and Jetty 12 EE 9 compatible test harness (i.e., one built from the forward branch of jenkins-test-harness) are used, the following test fails:
- hudson.plugins.git.GitStatusTest
One solution is e.g. https://github.com/jenkinsci/git-plugin/pull/1589 to migrate to using Mockito with Jetty 12 EE 9. Unfortunately, that approach is not backward compatible with Jetty 10 or Jetty 12 EE 8, so the PR will have to remain in draft until we release Jetty 12 EE 9 support. Still, we should prepare the PR in advance.
Alternatively, it would be more desirable if this test could instead stop using Mockito as in https://github.com/jenkinsci/view-job-filters-plugin/pull/58 and https://github.com/jenkinsci/configuration-as-code-plugin/pull/2494. That change could be prepared and released in advance without updating this plugin's core baseline.
- depends on
-
JENKINS-73278 Migrate core from EE 8 to EE 9
-
- Closed
-
- is blocking
-
JENKINS-73283 Run PCT with a Jetty 12 EE 9 test harness when core is Jetty 12 EE 9
-
- Closed
-
- links to
The master branch of the git plugin now includes fixes for GitStatusTest to remove the dependency on StaplerException. The tests were moved to GitStepTest and implemented using JenkinsRule.
Unfortunately, there is a new failure in the git plugin tests that is unrelated to Jetty 12 EE 8 or Jetty 12 EE 9 but may disrupt the Jetty 12 EE 8 and Jetty 12 EE 9 upgrade as well as disrupting the use of the Jenkins plugin bill of materials with Jenkins 2.462.1. I've submitted
JENKINS-73568and asked for some help to resolve it. I hope to have it resolved on the master branch of the git plugin before the release of Jenkins 2.462.1 so that git plugin 5.3 can be released with the test fixes needed for this issue.