On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof
<nicolas.del...@gmail.com> wrote:
> not inside the flow DSL, but inside jobs. build-flow is an orchestrator,
> it's not here to replace jenkins classic way to share artifacts between
> builds (fingerprints, copyartifact plugin, build number parameter, etc)
>
> collect executed jobs build object
>
> def b = build( "foo" )
>
> then pass build number as parameter to other jobs :
>
> build( "bar", artifactNumber: b.number )
>
> you should not try to use build flow as a groovy script executor. Even it
> don't restrict groovy syntax (maybe it should) it's a job scheduler DSL,
> nothing more.
But that means not thinking of it as a real jenkins job...
Conceptually I'm running the job to build some artifacts - in this
case as a somewhat more intelligent/controllable matrix job
replacement, so it doesn't make sense to me for the resulting
artifacts to have to end up in some other job's space. Could the DSL
be extended to have a 'copy child artifact' function so that after the
scheduling happen you can have the results where you'd expect jenkins
to have them?
--
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.
