build flow is a flightweight task, supposed to orchestrate jobs, not to archive content or manage a workspace. It can be triggered by commit hooks, best option.
2013/9/19 Les Mikesell <lesmikes...@gmail.com> > On Thu, Sep 19, 2013 at 12:16 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > I removed workspace in HEAD, previous version of plugin extend a classic > job. > > Doesn't the triggering svn check need that space? And probably other > triggering options, as well as the ability to archive anything it > produces? I don't understand how a job without a workspace or > archive coordinates with the rest of jenkins. > > -- > 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.
