Discussion:
Problem with Java 8 update 191?
James Fairweather
2018-10-29 22:27:55 UTC
Permalink
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?
--
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.
Mark Waite
2018-10-30 09:25:17 UTC
Permalink
Those workspace names are not an indication of an incompatibility. If
Jenkins needs to allocate a workspace and it detects that the default named
workspace is already in use, it will allocate a second workspace adjacent
to the first, with a digit appended to the workspace name.

Mark Waite

On Mon, Oct 29, 2018 at 11:28 PM James Fairweather <
Post by James Fairweather
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
D:\projects\lion\main
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
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/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
James Fairweather
2018-10-30 16:58:29 UTC
Permalink
Is there some way for me to find out *why* Jenkins thought the default
named workspace was already in use? Our scripts make assumptions about the
workspace location and if Jenkins appends something ("@2") to the name of
the folder it won't work.
Post by Mark Waite
Those workspace names are not an indication of an incompatibility. If
Jenkins needs to allocate a workspace and it detects that the default named
workspace is already in use, it will allocate a second workspace adjacent
to the first, with a digit appended to the workspace name.
Mark Waite
On Mon, Oct 29, 2018 at 11:28 PM James Fairweather <
Post by James Fairweather
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
D:\projects\lion\main
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
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/CALg80NUAJKSanpr_50wPoEusVQn0LCvN_10C81rZ2EewzjzdjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
M***@Diamond.ac.uk
2018-10-30 17:09:40 UTC
Permalink
It's very strange that Jenkins thought the workspace was in use, since you only have one executor on the agent. However, leaving that aside for the moment, why not use $WORKSPACE to get the name of the folder? Hard-coding the name is an anti-pattern that will be a problem if you ever want to use concurrent builds, or (I think) matrix builds.
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
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/790ba44d8a6e4fe7aa588abeff23e121%40Diamond.ac.uk.
For more options, visit https://groups.google.com/d/optout.
James Fairweather
2018-10-30 23:11:23 UTC
Permalink
Thanks for the suggestion of using $WORKSPACE, that's an improvement. I
still don't know why Jenkins thought the primary workspace was in use but
since the problem has disappeared, I won't worry about it for now.
Post by James Fairweather
Post by James Fairweather
Is there some way for me to find out *why* Jenkins thought the default
named workspace was already in use? Our scripts make assumptions about the
the folder it won't work.
It's very strange that Jenkins thought the workspace was in use, since you
only have one executor on the agent. However, leaving that aside for the
moment, why not use $WORKSPACE to get the name of the folder? Hard-coding
the name is an anti-pattern that will be a problem if you ever want to use
concurrent builds, or (I think) matrix builds.
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If
you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/790ba44d8a6e4fe7aa588abeff23e121%40Diamond.ac.uk
.
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/CALg80NUNcUuP_sR7_ZfVrpNqnQgrywEZUrRtm49ivw%2BfV4LFbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...