On Thu, Sep 19, 2013 at 10:16 AM, Slide <slide.o....@gmail.com> wrote:
> That's what I do. I have my hourly/nightly checks kick off a job that uses
> the Build Flow plugin to build other projects. It's worked very well for me
> so far. I had issues with the trigger parameterized build and other plugins,
> but using the Build Flow plugin in the method I described has been a life
> saver.
I can sort-of see how to patch the different bits of functionality
together, but I think it will confuse our users if they have to
trigger from one job, edit the workflow in another, and have their
results show up in yet another. I'm really looking for something that
works like a matrix job but permits a little more control over the
individual sub-jobs and the layout of the resulting artifacts (e.g.
when building libraries I'd like one snapshot copy of the include
header files plus each platform's .so/.dll/etc.).
--
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.
