Sorry missed the important statement: After each build, get the build number as B1.build.number
From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ginga, Dick Sent: Monday, September 16, 2013 9:44 AM To: jenkinsci-users@googlegroups.com Subject: RE: Build Flow Plugin and artifacts management in the DSL 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. From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Emmanuel Boudrant Sent: Monday, September 16, 2013 9:34 AM To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> Subject: Re: Build Flow Plugin and artifacts management in the DSL I am not sure it will work, copy Artifact plugin is going to only copy the last successful artifact of a given job ? When I launch N job in parallel they are actually the same job with different parameter. Could it copy the artifacts generated by each job build ? On Monday, September 16, 2013 6:09:06 AM UTC-7, rginga wrote: The Copy Artifact Plugin will allow your "deploy" job to copy artifacts from your other jobs and put them in the deploy workspace. From: jenkins...@googlegroups.com<javascript:> [mailto:jenkins...@googlegroups.com<javascript:>] On Behalf Of Emmanuel Boudrant Sent: Monday, September 16, 2013 9:04 AM To: jenkins...@googlegroups.com<javascript:> Subject: Build Flow Plugin and artifacts management in the DSL Hello, We've checked the Build Flow Plugin for parallel execution, is is possible to manage the artifact in the plugin. Example : parallel ( // Each job is going to produce one artifact { build("job1") }, { build("job2") }, ... { build("jobN") } ) // deploy need access to all the artifact generated by job1, job2, ..., jobN. build("deploy") Our use case is we have plenty of slaves for building the artifacts but only one slave can deploy them. Thanks, -emmanuel -- 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-use...@googlegroups.com<javascript:>. 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<mailto: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<mailto: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.
