Thanks Owen!!! It solves my problem perfectly! On Wednesday, 5 September 2012 09:07:58 UTC+10, Owen B. Mehegan wrote: > > Hi Jim - > > I'm a Jenkins jockey by day (nothing special by night). One way that you > could do this would be to use the Parameterized Trigger plugin: > https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin > > In DB-Migrator, add a *build step* (not a post-build step) of > "Trigger/call builds on other projects." Set up a trigger for DB-ORM (with > no parameters if none are needed) and select "Block until the triggered > projects finish their builds." This will then display some choices of what > to do if the next build fails, such as failing this build. > > Repeat this process in DB-ORM, having it run the build of ClientApp. > > With this setup, a failure of ClientApp would fail DB-ORM, which would > then fail DB-Migrator. > > Alternatively, you could look at the post-build action called "Aggregate > downstream test results," but I'm not positive this would work for you. > > I would also highly recommend that you check out the #jenkins IRC channel, > on the irc.freenode.net network (see http://freenode.net/ if you've never > used IRC). The core developers of Jenkins, as well as people like me, are > always in there. It is hands-down the best place to get quick answers to > questions. > > Hope this helps! > > On Monday, September 3, 2012 7:55:38 PM UTC-7, marsbomber wrote: >> >> Hi guys, >> >> This post isn't directly related to Ruby, but I thought I'll try my luck >> here anyway (mercy, moderators!!! :p) >> >> I want to get your opinions on the following. >> >> I'm setting up various build plans for various projects on Jenkins. Let >> me illustrate the situation with an example >> >> Projects: >> >> - DB-Migrator. This is a Rails app that handles database migrations. >> - DB-ORM. This is a Perl ORM lib that interacts with the database, >> which is controlled by DB-Migrator >> - ClientApp. This is a project that uses DB-ORM lib. >> >> To me, ClientApp is a downstream to DB-ORM, and DB-ORM is a downstream to >> DB-Migrator. >> >> Goal: I want to make a build plan that will FAIL DB-Migrator if and of >> its downstreams fail (any level). >> >> This is how you guys will structure it? And I cannot seem to make Jenkins >> fail DB-Migrator upon downstream failures... >> >> Thanks in advance! >> >> Cheers, >> Jim >> >
-- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To view this discussion on the web visit https://groups.google.com/d/msg/rails-oceania/-/FK3tVM2oCp4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
