You need a way to export the build numbers outside the build flow environment so that they are available to a later archive step.
I tried doing this but could not. I do not know DSL/Groovy/Jenkins enough to do it. -----Original Message----- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Les Mikesell Sent: Monday, September 16, 2013 10:51 AM To: jenkinsci-users Subject: Re: Build Flow Plugin and artifacts management in the DSL On Mon, Sep 16, 2013 at 8:44 AM, Ginga, Dick <dick.gi...@perkinelmer.com> wrote: > There are a number of ways to "pick" the artifacts to archive. Use the > > > > In your DSL, do > > B1 = build("job 1") > > B2 = build("job 2") > > > > Then pass them to Deploy as parameters. > > > > Then, as just stated, your deploy job can pick specific builds. This approach should work as long as the artifacts are copied by another job started after the builds complete. Is there any way for the parent build-flow job to collect (and then archive) them itself instead of having another job do it? I can't find a way to use the copy artifact plugin from a build flow job. -- 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.
