> Jetty 10 requires Java 11, so there’s one concrete reason to upgrade
sometime.
For sure. Right now there is no timeline for 9.x deprecation, but it is
likely to become a less maintained baseline with mostly backports. Actually
it may make Jetty more stable for a while, but there will be growi
Brief update on this:
* Mark has updated the website to use Java 11 install instructions
* Core caused illegal reflective access warnings PR is merged
* Stapler illegal reflective access was released in 2.273
* Remaining warnings are mostly caused by groovy which requires some work
to
upgrade, h
Initial attempt here to fix most of the warnings:
https://github.com/jenkinsci/jenkins/pull/5110
Rest of the warnings are caused by groovy and guice, at least on the
controller startup.
On Tuesday, 8 December 2020 at 03:18:39 UTC msi...@cloudbees.com wrote:
> Jetty 10 requires Java 11, so there
Jetty 10 requires Java 11, so there’s one concrete reason to upgrade
sometime.
On Mon, Dec 7, 2020 at 13:14 Matt Sicker wrote:
> Oh neat, that's good news! I hope they backport their ChaCha cipher
> code, too, because that's still only supported by BouncyCastle
> otherwise for Java 8 as far as I
Oh neat, that's good news! I hope they backport their ChaCha cipher
code, too, because that's still only supported by BouncyCastle
otherwise for Java 8 as far as I'm aware.
On Mon, Dec 7, 2020 at 12:26 PM James Nord wrote:
>
> > and it also natively supports TLS 1.3 which is fairly important
>
> and it also natively supports TLS 1.3 which is fairly important
for HTTPS as well as for securing inbound remoting agents.
FTR that should be available in recent OpenJDK releases.
https://bugs.openjdk.java.net/browse/JDK-8245466
On Fri, 4 Dec 2020 at 16:35, Matt Sicker wrote:
> It may be i
FWIW, whenever I need to set up some sort of integration testing with
Jenkins, I'm usually using Java 11 as it's what's most easily
installable on Linux and Windows. The only incompatibilities I've come
across so far have been old fixed issues in maven-hpi-plugin when
trying to compile old plugins.
Last time I was testing cross-JVM mode (Java 8 agents + Java 11
controller), it passed smoke tests I had. I am pretty sure there are class
serialization edge cases, but it should be solvable.
As Jesse said, the main concern is about warnings being printed here and
there. JVM access and illegal ref
I know there has been few/minor reports on IRC/gitter about agents having
issues in 11 that were fixed going back to 8. I tried to encourage them to
report issues, but I'm not sure they did.
On Fri, Dec 4, 2020 at 1:50 PM Jesse Glick wrote:
> I am definitely opposed to trying to continue to “sup
I am definitely opposed to trying to continue to “support” 8 if and
when we use 11 as a baseline for core. Let us be clear about what we
require and test against, so that we do not have a combinatorial
explosion of platforms. Plugins can be switched to run 11 in CI over
the course of a few months,
I agree but given the (often dangerously subtle) incompatibilities between
agents and controllers when they run a different jvm, we should do this
with a tight plan.
Maybe some of the features currently in version-column plugin should be put
inside the core so alerts and guidance are more systemat
I think defaulting the docker images to java11 would be a good start
On Fri, 4 Dec 2020 at 17:26, Baptiste Mathus wrote:
> I agree with Daniel's take: delay to do something for real not before mid
> 2021.
> And I think we can still definitely love forward in the meantime on a plan.
> Which this
I agree with Daniel's take: delay to do something for real not before mid
2021.
And I think we can still definitely love forward in the meantime on a plan.
Which this thread is great for brainstorming about (thanks Ulli).
For instance, we did switch ci.j.i to java 11 already.
I would think we want
It may be important to note that requiring Java 11 to run Jenkins
doesn't mean you can't still use it to build Java 8 (or older!)
projects.
>From a user point of view, I'd prefer that we can at least ensure that
Jenkins runs properly in the latest Java releases. Running a newer JVM
brings with it
> is there any advantages in java 11 your looking forward to
Personally I would change my code to use a HTTP client library that has
async support, SNI, (all the things you expect) and not rely on a third
party API that does not have stellar backwards compatibility :)
https://docs.oracle.com/e
I love getting rid of old frameworks / libraries / ... to take advantage of
all new stuff provides, but it's painful for users to migrate. The Java JDK
is like changing your foundations and with all those new pain-potential
changes we've made, I agree with Daniel, it's better to go little by little
> On 4. Dec 2020, at 09:43, Ullrich Hafner wrote:
>
> Ok, I understand that. I wasn’t aware that so may people are still using Java
> 8.
Jenkins stats (scroll down for recent months):
https://stats.jenkins.io/plugin-installation-trend/jvms.json
Obviously, Jenkins influences the stats here
As a non java person, Is there any advantages in java 11 your looking
forward to? ones that might encourage people to upgrade? I know streams and
lambdas were nice in 8(?)
its my understanding that most things should now compile with java 11, but
not bumping the minimum version yet.
Gavin
On Fr
Ok, I understand that. I wasn’t aware that so may people are still using Java
8. My students just ask me every time they want to contribute to my Jenkins
plugins why they still need to use that old Java version ;-)
> Am 04.12.2020 um 08:34 schrieb Tim Jacomb :
>
> I would be definitely +1 for s
I would be definitely +1 for switching defaults and encouraging people to
use jdk11
And not against updating the minimum version, people will move when they
have to.
At my previous work we moved from 7 to 8 when we had to and it was no
issue...
We’ve been on 11 for awhile here...
Java 8 is 6 ye
Yes, the Java 11 adoption is still very low. It was around 30% last time I
have seen the stats. Around 60% of users still run Java 8. With such a
state it does not make sense to drop the Java 8 compatibility without
really serious reasons which we IMHO do not have.
On a separate note, a few wee
There are not. Considering the relatively low adoption rate of Java 11,
I'd personally resist a move to make Java 11 the baseline for quite a while
unless there were some way to preserve and assure that Java 8 continues to
work as expected even with Java 11 as the baseline.
On Thu, Dec 3, 2020 at
Are there already plans to move the Java baseline from Java 8 to Java 11 in the
near future in Jenkins core?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an em
23 matches
Mail list logo
