That is exactly the problem. I have succeeded in deleting all workspaces, and disabled the concurrent builds option, but the workspaces (with @) keep showing up.
Even when there is only one build, it will create the folders <job_name> AND <job_name>@2. On Thursday, May 10, 2012 5:07:04 AM UTC-4, Jan Seidel wrote: > > This happens on simultaneous builds on one node > Just delete the workspace with the @<number> manually. That will else > remain and be used in the future -.- > After deleting the workspace will Jenkins start to use the default > workspace and everything will be fine again. > Configure your jobs that only one job of the same project may build at a > time. > > Take care > Jan > > Am Mittwoch, 9. Mai 2012 21:31:03 UTC+2 schrieb Eric Lordahl: >> >> When i reference the "WORKSPACE" variable in shell scripts there is an >> @<number> at the end. I notice this directory is used for everything i do >> during the build, but the SCM is in the directory without the @. >> >> The problem is when i attempt to archive some directories that i create >> during the build, they are not in the actual workspace because it checks >> the directory without the @. The new stuff ends up in the directory with >> the @2. >> >> Does anyone know why this happens? I can work around it, but want to >> know why it's happening. I don't have concurrent builds enabled, and this >> build is tied to one windows slave. >> >> Thanks in advance. >> >
