Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Using Buildreactor to Monitor CI Jobs

DZone's Guide to

Using Buildreactor to Monitor CI Jobs

· DevOps Zone ·
Free Resource

Best practices for getting to continuous deployment faster and with dramatic results in reduced outage minutes, development costs, and QA testing cycles. Brought to you by Rainforest QA.

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

Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}