On Wed, Sep 18, 2013 at 12:38 PM, nicolas de loof
<nicolas.del...@gmail.com> wrote:
> this is a voluntary limitation. Even flow uses groovy, it's supposed to be a
> DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you want
> to do such thing
OK, but how? I don't see the option to do another build step within
the job and if there were, how would I pass the parameters for the
child jobs and build numbers that build flow had just run? Another
separate job run as part of the flow will work, but it would just seem
neater to me if the top-level controlling job could collect all of the
artifacts into the desired layout by itself. In this particular
case I want it because I want to be able to run a custom 'promotion'
plugin that is going to commit to a subversion tag and it has to be an
atomic operation with everything in one tree, but just in general it
seems like you should be able to run the top-level job and have that
be the place where the artifacts show up (if you want) rather than
having some other job get them.
Or are you saying I should code up the whole sequence directly in
groovy instead of using build flow at all if I need the artifacts?
--
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.
