CI: Move to java 11
See original GitHub issueTell us your idea!
A java 11 installation is the prerequisite to use gradle 7 (see #11539). As in AS 2020.3.1 we have already a java 11 included as default java and it compiles successful our code with gradle 4.* I do not expect trouble.
Someone with direct access has to change the default java implementation.
I found a configuration at https://ci.cgeo.org/configureTools/, with directory /opt/jdk1.7.0_04/
.
What solution would you suggest?
No response
Is there an alternative?
No response
Additional Information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Migrating to Java 11 - CloudBees Documentation
The Jenkins LTS core that CloudBees CI is based on has been capable of using Java 11 for some time, but all core...
Read more >Building Java 11+ projects on Travis CI - Deps
Historically Java releases moved at a slow pace. Open source projects and companies could comfortably stay on the same version for several years....
Read more >It's time to move your applications to Java 17. Here's why ...
What you need to know about code migration from the previous Long-Term-Support versions of the platform: Java 11 and Java 8.
Read more >Use Java 11 in CI/CD Pipeline to Build Application Jar Files ...
You can still use Java 11 in your pipeline to build application deployable JAR file for Runtime Fabric deployment with Java 8 based...
Read more >Upgrading Jenkins Java version from 8 to 11
Upgrading Jenkins Java version from 8 to 11. There are a few details and steps to upgrade the JVM used to run Jenkins,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would say: Go for it…soner or later we need this upgrade anyway and if you happen to have time now, just do it.
executor-4 worked. I will let it run and update other executors in next days.