On 01/26/2015 11:15 AM, Les Mikesell wrote: > On Mon, Jan 26, 2015 at 12:42 PM, Don deJuan <[email protected]> wrote: >>>>> Something this complex sounds like a job for the workflow plugin and job >>>> type >>>> >>>> SNIP ..... >>>> >>>> >>>> OK thanks I will look into that. Open to any other advice or suggestions. >>> It's not clear to me from your post what actually determines what you >>> need to build. You need to understand that and then figure out >>> whether jenkins can find it internally or if you need some external >>> wrapper to kick off paramaterized builds of some sort. >>> >> It is part of the commit message in git. There is a script that parses >> the git log in post-receive that defines what needs to be built and what >> envs it should be built in. > > If you can map that into job parameters you should be able to trigger > individual jobs using > https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin > to control where each job runs, or use a matrix job where you kick off > a groovy or Xshell script (for cross platform compatibility) and the > script figures out what, if anything, it needs to do. The matrix > approach might make sense if most of the builds require multiple nodes > and you like the resulting artifact tree layout on the job page. And > the workflow or build_flow can handle more complex options if you need > them. > Ahh nice thanks for that.. I think things are becoming much more clear for me.
-- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/54C69578.5080704%40gmail.com. For more options, visit https://groups.google.com/d/optout.
