On Wed, Oct 30, 2013 at 7:48 AM, nicolas de loof
<[email protected]> wrote:
> scriptler is for groovy scripts
> build flow is (supposed to) offer a DSL to orchestrate job execution
>
> both make sense. Maybe you're looking for something "in the middle"
I'd like to create a more versatile 'matrix build' where the top-level
job can be triggered by an scm change and can collect the results from
child jobs into its own workspace. I think that could be done by
build-flow with separate helper jobs to start the run and collect the
results, but that seems messy and wrong. And it could be done in
pure groovy, but no one here knows the language well enough to do a
good job of dealing with all the possible error conditions, etc. I
think it would be great if the operations that build[-flow provides
were packaged as library routines you could use in a groovy build
step. I haven't looked at scriptler yet - if it has a simple way to
run other jobs in parallel and access their results that may be what I
need.
--
Les Mikesell
[email protected]
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
