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 matrix 1.8 #299
jenkins matrix 1.8 #299
Conversation
Removes Jenkinsfile's adds .jenkins.groovy
.jenkins.groovy
Outdated
values 'jdk_1.8_latest', | ||
'jdk_11_latest', | ||
'jdk_16_latest' |
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.
Currently in main:
Lines 39 to 41 in 4cebebb
values 'jdk_1.8_latest', 'adopt_hs_8_latest', 'adopt_j9_8_latest', | |
'jdk_11_latest', 'adopt_hs_11_latest', 'adopt_j9_11_latest', | |
'jdk_15_latest', 'adopt_hs_15_latest', 'adopt_j9_15_latest' |
values 'jdk_1.8_latest', | |
'jdk_11_latest', | |
'jdk_16_latest' | |
values 'jdk_1.8_latest', 'adopt_hs_8_latest', 'adopt_j9_8_latest', | |
'jdk_11_latest', 'adopt_hs_11_latest', 'adopt_j9_11_latest', | |
'jdk_16_latest', 'adopt_hs_16_latest', 'adopt_j9_16_latest' | |
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.
The maven bundle plugin doesn't build with 16, and there are some groovy compatibility issues too.
I think it's worth building up to Java 14 (there was a crypto alias change) for the time being on this branch, and keep main
building on 8, 11, and the last release (16 atm).
Thoughts?
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.
Ok, I think we can keep 14 for now.
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.
+1
There are a few issues with the maven plugins used in the 1.8.x branch, these issues have been resolved on `main`, and should be merged in a different PR (if they need to be back ported)
No description provided.