[Jenkins-infra] Moving ci.jenkins.io to Java 11

Baptiste Mathus ml at batmat.net
Wed Apr 3 10:08:39 UTC 2019


Given the GA was announced a few days ago [1], and ci.jenkins.io is running
on 2.164.1, I am strongly in favor of doing this.
We do not expect any issue by this bump, and if any, we should rather hit
them before our users.

This email is more to gather feedback about how people feel about this.

If people generally agree, then we will move forward to discuss what needs
to be done to assess that upgrade before actually doing it.
(For example: the very minimum/first step would be to install an instance
with the same set of plugins as in ci.jenkins.io, etc. + manually checking
the installed plugins to judge if we see any risk).

-- Baptiste
[1] https://jenkins.io/blog/2019/03/11/let-s-celebrate-java-11-support/

Le mer. 3 avr. 2019 à 11:17, Adrien Lecharpentier <
adrien.lecharpentier at gmail.com> a écrit :

> Hello,
> as we worked on making sure Jenkins could be run on Java 11, that we
> announced that and some of us are already running for some time our
> instances on Java 11, I'm wondering if we could move ci.jenkins.io to be
> run on Java 11.
> I'm asking here to have a discussion. If we think it would be fine, I'll
> open a infra ticket to track this work.
> If we have all the latest version of Pipeline plugins (workflow-support
> 3.0+ is the most important) on the instance, we should be fine. So other
> plugins had to be fixed, but they were almost all released with the fix.
> --
> Adrien Lecharpentier
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190403/448f304d/attachment-0001.html>

More information about the Jenkins-infra mailing list