Could be JENKINS-21622, fixed in 1.561.
https://issues.jenkins-ci.org/browse/JENKINS-21622
(Note that 1.561 -- and 1.560 -- seems to be not so great, so you might want to
hold off upgrading for a while.)
On 28.04.2014, at 15:42, Dirk Heinrichs <d...@recommind.com> wrote:
> Hi,
>
> we see some strange behaviour here where a job that is configured to run a
> single instance at a time ("<concurrentBuild>false</concurrentBuild>" in
> config.xml) sometimes creates a new workspace "jobname@2" next to the already
> existing workspace "jobname".
>
> My understanding is that this should only happen if the job was configured
> with "<concurrentBuild>true</concurrentBuild>".
>
> Any hints what else could be causing this behaviour?
>
> This is Jenkins 1.543 on Windows Server 2008R2.
>
> Thanks...
>
> Dirk
> --
> <Logo.gif>
> Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Tel: +49 2226 1596666 (Ansage) 1149
> Email: d...@recommind.com
> Skype: dirk.heinrichs.recommind
> www.recommind.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-users+unsubscr...@googlegroups.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
