8000 Test Java 11 directly · jenkinsci/github-plugin@6d8ef2f · GitHub
[go: up one dir, main page]
Skip to content

Commit 6d8ef2f

Browse files
MarkEWaiteMarkEWaite
committed
Test Java 11 directly
Address the concern that Oleg expressed in #368 (review) We've detected no regressions with the transition to testing Java 11 byte code as generated by Java 17 and Java 21 compilers in the 200+ plugins that have made the transition. We test with Java 11 on older lines (Jenkins 2.401.x and Jenkins 2.414.x) in the plugin bill of materials while testing with Java 21 on the most recent weekly release. We've detected no issues with any of the plugins that are included in the plugin BOM. We want to reduce Jenkins infrastructure costs by not testing configurations that are unlikely to detect issues. Testing with Java 11 is unlikely to detect issues and adds infrastructure cost. I've added Java 11 on Linux as a test configuration. I do not intend to make that same addition on the other 100+ repositories where we're testing with Java 21 and Java 17. When a plugin maintainer asks to continue testing Java 11, I'm willing to adapt that pull request.
1 parent dc2cb25 commit 6d8ef2f

File tree

1< 9769 !-- --> file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

‎Jenkinsfile

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
buildPlugin(useContainerAgent: true, configurations: [
22
[platform: 'linux', jdk: 21],
33
[platform: 'windows', jdk: 17],
4+
[platform: 'linux', jdk: 11],
45
])

0 commit comments

Comments
 (0)
0