James Fairweather
2018-10-29 22:27:55 UTC
Today I installed the version of Java from 8 build 181 to 8 build 191 on
several build slaves. After doing that, Jenkins started allocating a 2nd
workspace on the some of the build agents. For example, instead of running
here:
D:\projects\lion\main
They were running here:
D:\projects\lion\***@2
Each build agent has been allocated a single executor. We are running
Jenkins 2.138.2. I rolled the version of Java on the non-working agents
back to Update 181 and the problem went away.
Does anyone know if Java 8 Update 191 has some kind of incompatibility
problem with Jenkins?
several build slaves. After doing that, Jenkins started allocating a 2nd
workspace on the some of the build agents. For example, instead of running
here:
D:\projects\lion\main
They were running here:
D:\projects\lion\***@2
Each build agent has been allocated a single executor. We are running
Jenkins 2.138.2. I rolled the version of Java on the non-working agents
back to Update 181 and the problem went away.
Does anyone know if Java 8 Update 191 has some kind of incompatibility
problem with Jenkins?
--
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+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.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-users+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.