To be honest, I don't know myself if failing the upstream build is appropriate when a downstream fails...
If upstream project is treated as 3rd party lib (which is a big reason to modularise our internal codebase), then there's no reason to fail its build... BUT, BUT ... since control is all ours, when we make changes to an upstream project, we do not always keep backwards compatibility. That becomes a killer to all other projects that depend on this centre piece... So when I want to make a release of this upstream project, a green build of its own hardly gives me any confidence that the WHOLE system is in working order. This is the very reason that I want to see a big RED build for the upstream project. It will stop anyone from releasing it... Am I making sense here at all? On Wednesday, 5 September 2012 09:07:52 UTC+10, Simon Russell wrote: > > First off, to answer your actual question: I don't know how to set this > up. > > The main thing I wanted to say was that this doesn't actually make a > lot of sense to me; it almost seems backwards. You're basically using > ClientApp and DB-ORM as the tests for DB-Migrator. What if those > things break for a reason unrelated to DB-Migrator? If there are some > tests you think important, couldn't they be put into the DB-Migrator > app? Is it really that bad if ClientApp fails, and you look at the > failures and it turns out to be the migrator -- does it need to fail > everything? (DB-ORM in this case might be working perfectly.) > > Just my thoughts, clearly I'm not across the details of your project. > > Simon. > > On Tue, Sep 4, 2012 at 12:55 PM, marsbomber <[email protected]<javascript:>> > 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/-/nJBY_xK6wDMJ. > > To post to this group, send email to > > [email protected]<javascript:>. > > > To unsubscribe from this group, send email to > > [email protected] <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/rails-oceania?hl=en. > -- 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/-/aJjz9dnyVk0J. 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.
