-
Notifications
You must be signed in to change notification settings - Fork 166
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 LTS will drop support for Java 11 in October #3916
Comments
Yes, Java 17 is available but it looks like its not packaged as an RPM. |
@nodejs/build-infra Do we want to keep Debian 10 around in the CI or just remove? It's End-of-Life as of June 2024. (If we want to keep it, there are options for Java 17 -- both Oracle and Adoptium offer Java 17 that should work on Debian 10 AFAICT.) |
Debian 10 has the same glibc level as RHEL8 so it's technically feasible to keep that going as a functional system .... |
Another reason to remove Debian 10 is that npm 10.8.3 contains an update to node-gyp that now requires Python 3.8. The packaged version of Python on Debian 10 is 3.7.3. While it might be possible to install newer Python 3 on the machine by other means, that in combination with the Java 11 issue will add more maintenance overhead to keeping this End-of-Life platform active in the CI. Removal of Debian 10 will still leave Debian 11 and 12 in the CI, so we'll still have coverage on Debian there. |
On the release CI, I see only release-osuosl-centos7-arm64-1. Can we remove that builder? I see nothing in its build history. |
Yes, we don't use CentOS 7 anymore (from Node.js 18 onwards). |
FreeBSD is done. IBM i update: plan is for the machines to be updated to IBM i 7.4 next week. After that we (@abmusse ?) will need to update Jenkins and Ansible. |
Yes Once the machines get updated to 7.4 we will need to do some config changes to pickup Java 17. |
We now have Java 17 installed on the IBM i CI machines 🎉 |
CentOS 7 and Debian 10 machines were removed. |
https://www.jenkins.io/blog/2024/06/11/require-java-17/
After #3030 most of our agents are being run with Java 17.
Scanning through https://ci.nodejs.org/computer/ it looks like Java 11 is still being used on:
We can drop the CentOS 7 machine.
@abmusse Is Java 17 available on IBM i?
The text was updated successfully, but these errors were encountered: