Hello,
The latest Jenkins LTS release, 1.625, requires Java7 to run (to give some context, Java9 is in beta now, Java7 is many years old). As learned with some pain on ci.linaro.org, which already upgraded, this requirement applies not just to a Jenkins master, but also to build slaves, just to run slave agent to be connected to a master.
We install both Java6 and Java7 on android-build.linaro.org slaves, but the default is still Java6, "for compatibility with older Android versions", as a comment says.
Is Java6 being a default still relevant? The easiest way to accommodate the upcoming upgrade is just to switch default to Java7. If there're issues expected with that, we can follow an alternative way of adding adhoc version overrides for slave startup.
Hi Paul,
We can phase out java6 on android-build slaves. All our builds use java7 only nowadays.
Regards, Vishal On 04-Nov-2015 6:22 pm, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote:
Hello,
The latest Jenkins LTS release, 1.625, requires Java7 to run (to give some context, Java9 is in beta now, Java7 is many years old). As learned with some pain on ci.linaro.org, which already upgraded, this requirement applies not just to a Jenkins master, but also to build slaves, just to run slave agent to be connected to a master.
We install both Java6 and Java7 on android-build.linaro.org slaves, but the default is still Java6, "for compatibility with older Android versions", as a comment says.
Is Java6 being a default still relevant? The easiest way to accommodate the upcoming upgrade is just to switch default to Java7. If there're issues expected with that, we can follow an alternative way of adding adhoc version overrides for slave startup.
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Wed, 4 Nov 2015 18:38:35 +0530 Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Paul,
We can phase out java6 on android-build slaves. All our builds use java7 only nowadays.
Thanks Vishal, I switched EC2 slaves to use java7, and then plan to upgrade to Jenkins 1.625 at the end of day Friday.
Regards, Vishal On 04-Nov-2015 6:22 pm, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote:
Hello,
The latest Jenkins LTS release, 1.625, requires Java7 to run (to give some context, Java9 is in beta now, Java7 is many years old). As learned with some pain on ci.linaro.org, which already upgraded, this requirement applies not just to a Jenkins master, but also to build slaves, just to run slave agent to be connected to a master.
We install both Java6 and Java7 on android-build.linaro.org slaves, but the default is still Java6, "for compatibility with older Android versions", as a comment says.
Is Java6 being a default still relevant? The easiest way to accommodate the upcoming upgrade is just to switch default to Java7. If there're issues expected with that, we can follow an alternative way of adding adhoc version overrides for slave startup.
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
Hello,
On Wed, 4 Nov 2015 20:25:20 +0300 Paul Sokolovsky Paul.Sokolovsky@linaro.org wrote:
We can phase out java6 on android-build slaves. All our builds use java7 only nowadays.
Thanks Vishal, I switched EC2 slaves to use java7, and then plan to upgrade to Jenkins 1.625 at the end of day Friday.
Jenkins on android-build.lianro.org has been upgraded to 1.625.1. I made sure that both Docker and EC2 slaves start up ok and builds are running on them.
Regards, Vishal On 04-Nov-2015 6:22 pm, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote:
Hello,
The latest Jenkins LTS release, 1.625, requires Java7 to run (to give some context, Java9 is in beta now, Java7 is many years old). As learned with some pain on ci.linaro.org, which already upgraded, this requirement applies not just to a Jenkins master, but also to build slaves, just to run slave agent to be connected to a master.
We install both Java6 and Java7 on android-build.linaro.org slaves, but the default is still Java6, "for compatibility with older Android versions", as a comment says.
Is Java6 being a default still relevant? The easiest way to accommodate the upcoming upgrade is just to switch default to Java7. If there're issues expected with that, we can follow an alternative way of adding adhoc version overrides for slave startup.
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android@lists.linaro.org
-
Paul Sokolovsky -
Vishal Bhoj