>> 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.
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 [email protected].
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.
