This is my use case as well (slaves on EC2), and you are correct. I wouldn't want to copy the entire workspace to the master after every job (that would be quite time and disk space consuming), but not having it available later is annoying.
I've got items on my to-do list to investigate whether some of the plugins I use can be improved to not require the workspace to still be around, but this only addresses part of the issue. ----- Original Message ----- From: [email protected] To: [email protected] At: Mar 26 2013 16:02:16 OK, thanks for the explanation. In the case of using EC2 slaves that come and go quite frequently this seems to be problematic. I see there is a plugin that allows for copying from a slave to a master but even then it seems unlikely the workspace link would function correctly. On Tue, Mar 26, 2013 at 12:42 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) < [email protected]> wrote: > Yes, this is how it is expected to work. Access to the workspace is > performed through the open connection to the Jenkins slave on the node; the > workspace is not copied to the Jenkins master. This causes problems in some > areas; for example, the Warnings plugin does not copy referenced source > files to the master, it assumes they will still be available in the > workspace, which means if the node is not available, or the workspace has > been cleaned out, or the files have been changed, the linked-to file is not > available or doesn't match the warning. > > ----- Original Message ----- > From: [email protected] > To: [email protected] > At: Mar 26 2013 13:37:08 > > 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 <[email protected]> > 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 [email protected]. > > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/2Sfzzfz40T0/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Robert Moore Architect PIF Data K-12 Technology 400 Center Ridge Drive Austin, TX 78753-1034 D: 512.989.5476 (*Intra-Pearson: 22-5476*) M: 512.567.5192 * * *Pearson* Always Learning -- 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]. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
