Skip to content

Have you ever wanted to make the code coverage, compiler warnings or some other build stat more visible? Well, now you can!

screen shot 2017-01-15 at 22 38 05

This build brings a number of other improvements too:

  • The status of the External Build Jobs is displayed correctly (#265, #266) - thanks @hschink!
  • The animated build progress bar is displayed correctly in IE11/Edge (#272)
  • Even though the anonymous analytics were not gathered if you opted out, the script was still loaded causing an unnecessary HTTP request. This is no longer the case. (#276) - thanks @larsrh!
  • Instead of displaying the description of a failure set by the Build Failure Analyzer, Build Monitor now display its name making the information much more concise #275 - thanks @patrickdepinguin!

To set a badge:

  • Install the Groovy Post-Build Plugin
  • Add a Groovy Postbuild post-build action to a Jenkins project of your choice
  • Configure the Groovy script to call either:
    • manager.addShortText(textToDisplay) which sets a badge with default colours
    • manager.addShortText(textToDisplay, textColour, backgroundColour, borderWidth, borderColour) which sets a badge using custom CSS attributes. For example: manager.addShortText('Deployed', 'black', '#b4d455', '1px', 'green')

The above steps are documented in the acceptance tests, together with the accompanying screenshots.

The cool thing about the Groovy Postbuild plugin is that it has access to quite a lot of your build data via Jenkins core APIs, which you can see in their examples.

If you wanted to show the number of failing unit tests, for example, you could read the data from the TestResultAction object and configure the Groovy Postbuild action as follows:

def result =
def total  = result.totalCount
def failed = result.failCount

manager.addShortText(failed + " / " + total + " failed")

🗣 What information are your badges going to show? And how are you going to script it? Let me know on twitter and maybe we could compile a little cookbook for the Build Monitor Community :-)

You might be aware that I've been busy working on Serenity/JS, a next generation acceptance and regression testing library.

If you're working with modern web apps and have "learn some new tools" on your list of New Year's Resolutions or you're interested in doing acceptance testing at scale, please check out and let me know what your think!


Do you find Build Monitor useful? Support its development :)

Give it a star! ★
Found a bug? Raise an issue or submit a pull request.
Have feedback? Let me know on twitter: @JanMolak

Assets 3

@jan-molak jan-molak released this Nov 12, 2016 · 102 commits to master since this release

Hello and thanks for keeping your Build Monitor up to date, you're awesome! 👍

This release introduces changes to how the builds are rendered to help you better distinguish aborted, failing and disabled builds:

  • aborted builds are no longer rendered as failing (#260, #264) - thanks @deiga!
  • disabled builds are easier to distinguish from aborted ones as their names are now struck-through
  • oh, and Build Monitor also supports IE's Compatibility View (#259) - thanks @GMZwinge!

Plug: If you're interested in automated acceptance testing of your JavaScript and TypeScript projects, you might want to check out Serenity/JS - my latest open-source library, featured in DZone and presented at Devoxx 2016 last week.


Do you find Build Monitor useful? Support its development :)

Give it a star! ★
Found a bug? Raise an issue or submit a pull request.
Have feedback? Let me know on twitter: @JanMolak

Flattr Button

Assets 3
Oct 4, 2016
Release candidate v1.10+build.201610041454

This release comes with quite a few new features, bug fixes as well as performance and accessibility improvements. Sit back, grab a cup of your afternoon hot beverage of choice, ask Jenkins to upgrade Build Monitor to the latest version and enjoy reading the release notes ;-)

It's all in the headline

With this release, Build Monitor will tell you quite a few new things about your builds!

For example:
aborted build

  • When a build gets aborted, you'll know who aborted it. Also, an aborted build is now easier to distinguish from a failing one (#103, #218)
    new headlines
  • When a build is fixed, the brave engineer who fixed it can have their moment of glory when their name appears on the screen - thanks for the idea @yveshanoulle and for the implementation @ChadiEM 👍 (#202, #250)
  • When a build contains new code changes, you'll know whose changes are being built (#164)
  • ... or not! Because displaying people's names is now optional, so if you prefer Build Monitor to be a bit more discreet and keep this knowledge to itself, untick the "Display committers" option in the Build Monitor view settings (#243, #203).

Having said that, please remember that claiming a broken build also hides the names of possible culprits! It is also a great way to show that someone is actively working on addressing the failure.

html in description

You've also asked for the Build Monitor to support HTML content set using the Build Description Setter Plugin, such as links. Good news, you can do this now too! (#238, #222).
By the way, to prevent any XSS vulnerabilities, only regular, safe HTML works.

OK, so now onto the accessibility features!


reduce motion in accessibility settings

- The amount of animation Build Monitor uses can be reduced to make the screen a bit easier on your eyes when there are multiple jobs in progress. You can enable this feature by ticking **"Reduce Motion"** in the settings (#184) - You've probably also noticed the new slider component? I've replaced the old one in favour of [rzSlider]( as it **supports click events** and it's much easier to use on smart TVs (#217) - A bug that caused the state of "Colour blind mode" setting check box to be reflected incorrectly when the browser was reloaded got squashed now too.


There are quite a few improvements here as well:

  • Build Monitor needs much less CPU power, which should make the life of Raspberry PIs and laptop batteries a little bit easier (#230)
  • Also, the memory consumption over prolonged sessions on machines with no access to the Internet has been reduced (#200)

I've also done a lot of work refactoring the codebase so that it's easier to introduce new features and make Build Monitor even more useful, for example:

  • the project no longer uses the ancient Angular 1.1, it's now on nice 'n' shiny 1.5.8
  • a JobView model is now a composite of different features that a job might have. This should make adding support for pipelines and folders a lot easier.
  • also thanks to @SosoTughushi for helping out with making Sonar happier 😃 (#236, #237)
  • and to @TobiX for potenially resolving the problem with proxy servers cashing the CSRF token (#166)

Phew, that was quite a bundle!

Please upgrade your Build Monitor as soon as you can, give this project a ★ if you find it useful and feel free to ping me on Twitter @JanMolak if you have any questions or feedback!

All the best,
Jan Molak

I've been getting plenty of positive feedback and quite a few questions after my talks on the Screenplay Pattern and scalable BDD.

I've also answered some of the questions related to applying SOLID design principles to acceptance tests in this article. So if you still have your hot beverage of choice, I invite you to finish it while reading the article and tell me what you think in the comments! 😃

Do you find Build Monitor useful? Support its development :)

Give it a star! ★
Found a bug? Raise an issue or submit a pull request.
Have feedback? Let me know on twitter: @JanMolak

Flattr Button

Assets 3

This release brings support to some of the new features of the Build Failure Analyzer Plugin, closing #148, #170 and #228.
In short, you can now provide your fellow devs with more detail when the reason of a build failure is found.

How do you do this? As I continue to replace a traditional user guide with acceptance tests, I'll suggest that you follow an example from the new acceptance test: "Displaying the number of failed tests" and let me know if you found it easy to follow 😃

Of course, displaying the number of failed tests is just one example usage! Will you use this feature for any other purpose? Let me know!


I'm looking forward to hearing your thoughts on the latest changes, and don't forget to 👍 the ideas and suggestions you'd like to see implemented next!

Oh, and one more thing! I'm planning to write an article on how the Screenplay Pattern and Serenity BDD are used on Build Monitor. If you don't want to miss it, follow me on Twitter and Medium!

Jan Molak

Do you find Build Monitor useful? Support its development :)

Give it a star! ★
Found a bug? Raise an issue or submit a pull request.
Have feedback? Let me know on twitter: @JanMolak

Flattr Button

Assets 3
You can’t perform that action at this time.