Unstable Builds and the New Colour Scheme
This release brings support for "not built" and "unstable" jobs as well as UI improvements for Firefox. There's also a little announcement, so read on! :-)
UI improvements for Firefox:
- #95 - thanks to @kriserickson's contribution, job titles are vertically centred and progress bars pulsate the same way as they do in Chrome
Support for "not built" and "unstable" jobs and a changed colour scheme:
- #9, #58 and #88 - after a long discussion and many helpful suggestions from the community, Build Monitor now distinguishes the "not built" and "unstable" statuses from "failing". Here's the new colour scheme:
Claimed builds in both regular and colour-blind friendly mode share the same patterns to make it consistent.
If you're wondering what "claiming a build" means, check out this answer.
The above sounds like a simple change, right? There was a good reason why Build Monitor didn't distinguish between "unstable" and "failing" jobs initially though. Could your team be suffering from a bad case of rotting builds? Interested in learning more? Check out my recent blog post.
Did you manage to read this far? Brilliant, there's one more thing.
You can now look under the bonnet of how Build Monitor itself is built and delivered:
- thanks to the CloudBees FOSS program and their dev@cloud service, Build Monitor is continuously built and delivered using a publicly available Jenkins instance. What this means to you is that on top of all the builds released to the Jenkins Update Centre (such as this one) you can also get hold of pre-release builds, so please get in touch if you'd like to be notified when a new one is available
- plus, all the test results demonstrating the behaviour of the plugin with pretty SauceLabs videos are now easier to access from the Jenkins instance itself
Looking forward to hearing from you!