-
Notifications
You must be signed in to change notification settings - Fork 35
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
Update CI to use multiple Java and Groovy versions #267
Comments
I haven't really seen many problems with Java versions to make that worth adding time to the builds for (or complexity of cros-product) IMO. So, I'd probably say just test with whatever is the latest LTS. I think we should have a test for the latest of each major version of Groovy still supported by the team. At the time of writing, that would be
|
Can try with two versions (latest 3.x and latest 4.x). |
Ah, good point. Maybe we just do 11 across the board. |
Fixed on 981d4e7 |
The CI could be updated to a newer setup-java action which includes:
Maybe enhance some parameters (memory, no-transfer-progress), etc.
WDYT?
The text was updated successfully, but these errors were encountered: