[ANNOUNCE] Jenkins Upgrades to Java 8

[Baptiste Mathus]

Hello,

Please read the announcement on https://jenkins.io/blog/2017/01/17/Jenkins-is-upgrading-to-Java-8/, especially if you are still running Jenkins on Java 7 VM.

Thank you

[Staffan Forsell]

Will this also mean that the agents/slaves will require java 8? Will the ssh-slaves plugin install a java 8 jre if one is not available?

We have some slaves building on stuff on Ubuntu 14.04 LTS (and older...) which still does does not have a backported java 8 (See https://bugs.launchpad.net/trusty-backports/+bug/1368094). This is a Ubuntu LTS release with 2 years of support left which is used as the base OS for some machines, hence the reluctance to upgrade or use non standard package repositories.

We have java 8 support on mainline but we still need long term support for branches of delivered machines and these branches are built using jenkins.

So basically will it be possible to still run ssh slaves on OS:es not-supporting jdk8 by default?

/Thanks

Staffan

[Baptiste Mathus]

There's a strong debate about this. I would recommend not doing so (mixing versions). I've seen again a ClassFormatError happen in a production system because of that (JDK7 on agent, JDK8 on master). It will happen to work, but might start failing probably when you don't expect it. This is probably not worth the risk.

For your question, just checked again: being a fan of config mgmt myself and so, I understand the desire to use official upstream packages. But sometimes, you have to diverge for various reasons.

I just tested it and this works totally fine on Ubuntu:14.04 : download JDK from http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html for your system, uncompress it, add its bin directory in the PATH, done you have a JDK8 on 14.04.

And if really, you are using a special system, far more funky than that, as Jesse said already: you can then just connect to those using ssh during a build, and would work perfectly fine too.

HTH

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bcdf871b-8cc7-4e29-a139-e85a8b8e37d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Waite]

I agree with Baptiste.  Don't mix JDK versions between master and agents.  I had the illusion that the git plugin worked across that environment until a bug was found which shattered that illusion.

Mark Waite

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bcdf871b-8cc7-4e29-a139-e85a8b8e37d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6qjH5DQvTpRix_hWcSLm_meuz59L%3D__j7k3GqcwTWH4g%40mail.gmail.com.

[Staffan Forsell]

I'm thinking that we might solve it by having pipelines running in docker.

That way only the docker host will have to have jdk8 installed and everything else will be scripted. Maybe it's a good push for us moving towards pipelines for all jobs, not just actively developed ones.

/S

[nicolas de loof]

pipeline (and docker-pipeline plugin) still rely on a plain java jenkins agent running on build node. 

so this won't change the migration issue for people with exotic hardware. 

Anyway, JDK8 is available for most platforms, maybe not in the default upstream repository, but - hey - is this such a pain to download from Oracle ?

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/de986dc9-ea73-4cc2-9f7f-c4ed15fbffc6%40googlegroups.com.

[Baptiste Mathus]

Quick reminder. This is upcoming. 

The first weekly requiring Java 8 to run is expected very soon, in April is the plan.

Cheers

[James Chapman]

Very late to the discussion (especially as this was posted on the dev list almost a year ago) but as I have a number of old Jenkins nodes on various *nix platforms and architectures, the move to 1.8 is not something I look forward to.

Installing Java 1.7 on old versions of Solaris and FreeBSD was an absolute PITA when support for 1.6 was dropped, and only just manageable, trying to do this for 1.8 is going to be near impossible and those old distros are required for product compatibility testing. 

In short, will the move to 1.8 require Jenkins nodes to be upgraded too?

James

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6ie1UeUXzvxeg0dP6DmiJ7h-6vDemYAMY4do2JsXrRSw%40mail.gmail.com.

[Baptiste Mathus]

In short, yes. Agents cannot use an older JVM version than the one the Master node was compiled for.

It will appear to work, but will crash at some point.

So, as Jenkins core is compiled with Java 8, agents must run Java 8 or more (which is basically Java 8 only for now).

In your case, you want to look into simply connecting very old nodes using SSH. We already discussed that on the dev list a bit. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAHvkzym8ppeO5H8zdC%2BY9khySm_JZ1%3DsnTo6LeLV2GT0iBryjg%40mail.gmail.com.

[Baptiste Mathus]

Hello, quick heads up: next Monday, in a few hours from now, this will be effective.

Jenkins 2.54 will require Java 8. And there's a good chance next LTS baseline chosen for around next June will then require Java 8 too.

Thank you.  

[Baptiste Mathus]

2.54 is out and now requires Java 8 to run: https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/

[Pieter-Jan Busschaert]

Hello,

We use the debian packages from https://pkg.jenkins.io/debian/ and upgraded to 2.54 today. I assumed (wrongly) that these packages would contain the necessary dependency information so everything would "just work". This is not the case, as the .deb file contains only a data section (with the installation files), but no config section (which has the dependency information). Would it be possible to have these .deb packages mention the need for Java 8? In that case a normal update should just pull in the new required Java version (at least on the master).

Kind regards,

Pieter-Jan

 

[Baptiste Mathus]

Heads up: next LTS 2.60.1 will require Java 8, and will be released later this June.

--

You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3b2685b3-41a6-46a8-9047-3003b39ecb8b%40googlegroups.com.