Thank you Mark and Daniel, for the ideas.

I was able to go through every job, since it is a new jenkins setup with
not that many jobs. _None_ of the jobs uses custom workspace at all.

I did find out in one of the jobs, when defining git advanced behaviour for
cloning in to a sub directory of current workspace, there is something like
"${NAMESPACE}/${PROJECT_NAME}". But this job has not been run during times
the problem happened. And even if this statement is evaluated to "/",
according to what is said in the tips popup, this will be relative to the
job's workspace.

I tried to correlate the time when the slave tried to delete "/" and the
time jobs were running on the same slave, there seems to be no correlation
between them at all.


-- 
Vänliga hälsningar/Best regards,
Jifeng Zhang

-- 
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/CAJGt1%3DCWYHBa29svEfY5Jrz3-eKUYbQSvHSEHJRZWUMz2HmW3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to