DevOps Zone is brought to you in partnership with:

Dan Haywood is a UK-based freelance consultant specializing in enterprise application development using domain driven design approaches and agile development. Technology skills include Java, JEE, .NET, Sybase, RDBMS, OOAD, UML, AOP, TDD, Subversion and TFS Dan is a committer and advocate of the Naked Objects framework, and the author of “Domain Driven Design using Naked Objects”, published by the Pragmatic Bookshelf. Dan is a DZone MVB and is not an employee of DZone and has posted 15 posts at DZone. You can read more from them at their website. View Full User Profile

Using Buildreactor to Monitor CI Jobs

07.18.2013
| 1915 views |
  • submit to reddit

Following on from yesterday’s post (using travis-ci for github projects), I thought I’d use a Chrome plugin to monitor their status. The one I chose was buildreactor (itself hosted on github).

Like Travis-CI, buildreactor is also ridiculously easy to configure. Let me show you in pictures:

buildreactor-010

buildreactor-020

Once configured, the status is easily viewed (and buildreactor will also notify if a build fails):

buildreactor-030

I also was able to configure a separate account on travis-ci (for Estatio):

buildreactor-040

And I could also point buildreactor to our original cloudbees CI for Estatio, running Jenkins:

buildreactor-050

Published at DZone with permission of Dan Haywood, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)