-
Bug
-
Resolution: Won't Fix
-
Trivial
-
None
-
Platform: All, OS: All
I have a job that's responsible for generating documentation on one slave in
particular (kind of a utility job).
After switching to `concurrent-build`, the workspace appears to be unavailable,
I am greeted with this error:
"Error: no workspace
The project was renamed recently and no build was done under the new name.
The slave this project has run on for the last time was removed.
The workspace directory (null) is removed outside Hudson.
Run a build to have Hudson create a workspace."
While rebuilding definitely rebuilds the workspace, I feel this is worth
mentioning (we don't put too much valuable in the workspaces, but what if we did!)