-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-73282] Run PCT with a Jetty 12 EE 8 test harness when core is Jetty 12 EE 8 #675
Conversation
public boolean check(@NonNull BeforeExecutionContext context) { | ||
VersionNumber winstoneVersion = getWinstoneVersion(context.getConfig().getWar()); | ||
if (winstoneVersion.getDigitAt(0) < 7) { | ||
return false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do nothing if Winstone is Jetty 10 …
if (winstoneVersion.getDigitAt(0) < 7) { | ||
return false; | ||
} | ||
return super.check(context); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
… but otherwise invoke the logic in the superclass, which dynamically updates jenkins-test-harness.version
to 2230.v4fa_477b_634f4
, but only if the current value of the version is older (newer values don't need to be overridden).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
See JENKINS-73282. This PR has no effect for trunk, but once core adopts Jetty 12, this will dynamically upgrade the test harness to a Jetty 12 test harness (but only if necessary). The minimum test harness release is https://github.com/jenkinsci/jenkins-test-harness/releases/tag/2230.v4fa_477b_634f4 which supports Jetty 12 EE 8 and EE 9. This will allow plugins to be tested on Jetty 12 in PCT without having to upgrade each plugin's parent POM individually. Of course, once the plugin parent POMs are updated, this will have no effect. Eventually this code can be deleted once all plugins are on a plugin parent POM that includes Jetty 12 in its test harness.
Testing done
Tested with the latest weekly core as well as a Jetty 12 EE 8 core. In the latter case, the test harness was automatically upgraded as expected. Tested interactively in BOM in jenkinsci/bom#3314.