I see the same behavior and certainly assume it is by design. The workspaces are likely still there and can be accessed directly if you're on that node itself, just not through Jenkins.
Scott On Tue, Mar 26, 2013 at 12:30 PM, Robert Moore <robert.mo...@pearson.com> wrote: > This behavior seems new to me but perhaps I've just overlooked it in the > past. We are building slave nodes and after the nodes have gone offline are > not able to access the workspace (we see "Error: no workspace" when trying > to access it). Is this by design or a bug? > > Thanks, > > Rob > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
