--
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/291EDBE6054F46C6BA60EBE29665EBBB%40skyline.pino.net.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAFNCU-8zj%2B94TLh20FwMDWGtbiytSUGXy66cJ9hcDQ5a3aaywg%40mail.gmail.com.
For the record, the other announce about this: https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/ where we also pointed out what Arnaud perfectly summed up already.NIT: since 2.x we officially have switched from using "slaves" to using "agents" term.
2017-06-24 10:45 GMT+02:00 Arnaud Héritier <aher...@gmail.com>:
In short noJenkins master and slaves have to be launched with Java 8.Java 7 and older can still be used for builds
On Sat, Jun 24, 2017 at 7:27 AM, Conrad T. Pino <CP...@vflyer.com> wrote:
- A secure Java 8 JRE is unavailable on CentOS 5.
- Oracle JRE free support ended long ago.
- OpenJDK 8 binary packages unavailable.
- Fedora EPEL latest is OpenJDK 1.7.0_131
- Can Jenkins 2.60.1 work with Java 7 JRE slaves?
--
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/291EDBE6054F46C6BA60EBE29665EBBB%40skyline.pino.net.
For more options, visit https://groups.google.com/d/optout.
-------Arnaud HéritierMail/GTalk: aheritier AT gmail DOT comTwitter/Skype : aheritier
--
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/CAFNCU-8zj%2B94TLh20FwMDWGtbiytSUGXy66cJ9hcDQ5a3aaywg%40mail.gmail.com.
--
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/CANWgJS5mCWvouk4FvUUg0gDLpin1EqhhJOF6btkuxoy37gpddw%40mail.gmail.com.
Sounds like you need something that isolates the "Jenkins Slave" functionality from your build environment. I see these solutions:
A new machine with the Jenkins Slave that does SSH to your CentOS
5 build environment in the build step.
Put your CentOS 5 build environment in a Docker container and use one of these plugins:
* Docker Slaves: This plugin is marked as experimental and has
not seen any updates this year. It works with some kinks. E.g.
There is no limit on how many nodes it can start at once when
using pipeline. This dynamically provisions a full slave for each
build.
* Cloudbees Docker Custom Build Environment plugin. This plugin has not seen any updates for a couple of years, but a new maintainer is getting started now. This plugin attaches on an existing slave and uses the Jenkins Slave mechanisms for scheduling. It lacks pipeline support and does not work if the slave itself is running as a Docker container.
/Jacob