Thanks, I think I must have been building multiple jobs at the same time.
It's no longer an issue, so it must have been while I was configuring the
job and running the job very frequently to test my configurations and
scripts. It's now building in one workspace and not creating new ones.
On Fri, D
Check and see if you have allowed concurrent builds on this job. That's
what Jenkins will do to avoid workspace collisions with concurrent builds.
Eric
On Dec 12, 2014 6:35 PM, "Leah" wrote:
> Hi, I have a Jenkins freestyle job that is creating a new workspace each
> time I run it. Each workspac
This should only happen if you configured the job to run multiple builds in
parallel.
If that's not the case:
0. Make sure Jenkins is up to date. This one should be really obvious. If
you're on 1.560 or lower, this may be JENKINS-21622.
1. Check the system log at the URL /log/all to see whethe
That form of workspace naming is typically used by Jenkins when more than
one build of the same job is running at the same time. If you've enabled
concurrent builds for that job, then you may see workspace names with
numbers appended.
Mark Waite
On Fri, Dec 12, 2014 at 4:35 PM, Leah wrote:
>
>
Hi, I have a Jenkins freestyle job that is creating a new workspace each
time I run it. Each workspace is named workspace@. I am not sure
how to eliminate this procedure as I have trying to attach a file from the
original workspace and it is not possible when it build in a new workspace
each time.
