Closed mawHBT closed 2 years ago
When I execute a peass-ci job with Java 17, I get the following error: https://nopaste.net/7EguUtss5a it seems to me like Jenkins is still not ready for Java 17, even if its now in preview state (https://www.jenkins.io/blog/2022/03/21/java17-preview-availability/). I think we should postpone this issue until Jenkins officially fully supporting Java 17.
Peass-CI itself has also problems running on Java 17, so I created an issue: https://issues.jenkins.io/browse/JENKINS-68860
According to https://www.jenkins.io/doc/administration/requirements/upgrade-java-guidelines/, updates to Jenkins versions above 2.357 (including our current LTS 2.346.1) will render our plugin unusable for Jenkins running on Java 8 (adding a Java 8 JVM for runs should still be possible). This should be noted.
According to https://issues.jenkins.io/browse/JENKINS-68860, we should update to parent version 4.40. I did this, but the Java 17 errors still appear.
This should work with the current Jenkins version. Does this work for you?
I built peass-ci, running all tests locally. Worked for me.
Ok, so I'll close this issue.
What feature do you want to see added?
Building peass-ci with java-17 on ubuntu works, if you skip the tests. If you don't, you get various errors, e.g.:
Peass-ci should be made fully compatible with java-17.
Upstream changes
No response