I removed workspace in HEAD, previous version of plugin extend a classic job
2013/9/18 Les Mikesell <lesmikes...@gmail.com> > On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > build flow don't have a workspace, so no place to store child artifacts. > > you could trigger a final job to collect other ones artifacts using > > copy-artifact > > That's, ummm, interesting... I see a workspace in the jenkins job > view containing the svn version checkout that triggered the job and > 'archive artifacts' post-build step works to save any of those files > into the master archive (we usually archive the .h files along with > built libraries). Can't it copy into that space? > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > 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.
