Err, no.
A "workspace" is where slave doing its work.
But artifacts made by job(s) are stored in separate place.

By analogy to real life: you have a workshop where you produce things,
and storage where you put them after.

On 24 October 2012 00:43, Levente Uzonyi <leves at elte.hu> wrote:
> Isn't the issue simply that Jenkins is looking for the workspace at the
> wrong place? When we first set up our Jenkins instance it created the
> workspace directory at a different place than what the documentation[1]
> says. There was a workspace directory in the JENKINS_HOME directory with
> subdirectories for each job IIRC. After the first restart it was looking for
> the workspace directory at the place suggested by the documentation, so our
> jobs "disappeared". We fixed the directory structure by hand and everything
> is fine since then.
>
>
> Levente
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins
>
>
> On Tue, 23 Oct 2012, Chris Cunnington wrote:
>
>>
>> I think I can sketch out a few details.
>>
>> 1. The first thing is that this is not a medical emergency. I'm saying
>> that for my own peace of mind. System administration under duress is no fun
>> at all.
>>
>> 2. The builds are still there. They don't disappear. They just aren't seen
>> by the webpage. We are not alone in this. It has happened before.
>>
>>
>> http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-11938-Jenkins-loses-builds-when-restarted-td4124991.html
>>
>> 3. The problem may be in the reading of an XML file. The solution I've
>> gleaned so far is that instead of creating another build, I could log in and
>> press:
>>
>> "Reload Configuration from Disk"
>>
>> Or I could just try restarting.
>>
>> 4. This didn't happen on the older server. It won't last forever on this
>> one.
>>
>> 5. God knows, somebody will come up with a better answer than I can. But
>> since you're all looking at me at this moment, I say this: "Don't panic. We
>> still know where our towel is."
>>
>>
>> Chris
>>
>
>
>



-- 
Best regards,
Igor Stasenko.