Jenkins Build Monitor Plugin Versions Save

This release makes the Build Monitor UI just a little bit smarter:

• The base size of the font is automatically adjusted based on the number of dashboard rows displayed (closes #165 and quite possibly #172)
• You can still tweak the size of the font to make it up to 3x smaller or 2x larger than what's suggested
• If the number of widgets displayed becomes greater than what can comfortably fit on the screen, the dashboard becomes scrollable (closes #124)

Oh, the versioning scheme has changed to decouple the Build Monitor version number from the environment where the project is built (i.e. the Jenkins build number).

Now, instead of <major>.<minor>+build.<build number> you'll see <major>.<minor>+build.<timestamp>.

By the way, if you'd like to find out how to make Maven version your project in a similar fashion, check out my new Release Candidate maven plugin and the new pipeline.groovy Workflow script I use to build the Build Monitor to see how to use Release Candidate with Jenkins (or any other CI server for this matter).

As always - I'm looking forward to hearing your thoughts and hope that you find Build Monitor useful!

Best, 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

You can also sponsor a feature on bountysource!

Hello!

This version of Build Monitor brings quite a few changes, so grab your beverage of choice and enjoy reading the change log :smile:

• The way "culprits" are displayed has been changed significantly to address issues #138 and #151.
  Turns out that Jenkins doesn't cache culprit names and looks them up every single time the #getCulprits method is called. As there is no caching built-in and the call itself is expensive, this resulted in Build Monitor taking a performance hit in situations where a build's been failing for a long time and there was a large number of committers who pushed their changes over such broken build... Now, even though committing over a broken build or leaving it broken are "Bad Things To Do"®, this is no excuse for Build Monitor being sluggish ;-) As the second conclusion I came to was that displaying a long list of culprits wasn't particularly useful anyway, the new approach is this:
  If the build is broken - display the author(s) of the offending commit: If there's a number of failed builds, display how many exactly:
• To help you keep up to date, Build Monitor will now check if there's been a new release since your last update and display a subtle notification if that's the case:
• Also, the version of your Build Monitor is displayed in the footer so you don't have to be a Jenkins administrator to see if you're up to date:
• Another thing is that in order to help avoid performance issues and better understand how Build Monitor is used out there in the wild, the app will now gather anonymous usage statistics.
• One last thing is that this release also brings a fix to #183, which prevented Build Monitor from loading its UI assets if they're stored on a shared Windows network drive defined using a UNC path.
• OK, maybe one more thing: Build Monitor is now using the Release Candidate Maven plugin which helps with retrieving and setting the project version during the CI process, if you're using Maven and doing Continuous Delivery you might want to check it out!

I hope you like the new features and fixes. Looking forward to hearing your thoughts on Twitter!

Best, Jan

---

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

You can also sponsor a feature on bountysource!

Bug squashing session continues!

Due to a bug that crept into the CSS, error dialogs were not shown correctly. This build fixes the problem and should prevent issues such as #171 from occurring again.

---

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

You can also sponsor a feature on bountysource!

Some users of the newer instances of Jenkins noticed errors in the JavaScript console thrown by the hudson_behavior.js script (#182).

This release removes dependency on that script, so the JS console should stay nice and clean.

---

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

You can also sponsor a feature on bountysource!

This build brings a fix to issue #181, which prevented the jobs from being displayed if they were sorted by status, but the job status returned by Jenkins was null. Gotta love them nulls..

Also, the elapsed build time, typical build time and last execution time fields of each job widget now have a little tooltip explaining what they are.

More coming soon, stay tuned! :smile:

---

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

You can also sponsor a feature on bountysource!

By default, every broken build displayed on the Build Monitor is accompanied by a "list of possible culprits". This list is a list of people whose commits might have contributed to a broken build.

The purpose of displaying this information is to provide a point of contact to whoever has touched the broken build last and should (hopefully) be able to fix it the quickest :-)

However, if you'd rather not have this list displayed - you can disable it in the settings.

This release closes #70, #116 and partially addresses #138.

---

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

You can also sponsor a feature on bountysource!

This release teaches the well-known bottom-right corner of the job widget some new tricks (#63, #120, #20)!

When the build is not running it'll show you how long it's been since the last run (either successful or failed):

When the build is in progress, the widget will tell you how much time has elapsed since the build was started and how long it usually takes to complete it:

Love it? Want more? Let me know! :-)

---

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

This version of Build Monitor enables ordering build jobs by full name (including the CloudBees Folder name) - thanks to @luke-tsekouras-sirca for #122!

It also fixes a NullPointerException that has been observer when Jenkins is deployed to a Tomcat container (#125) - thanks to @ndeloof for reporting the issue and submitting the fix :)

Would you like to be able to sort the build jobs by other properties as well? Submit a pull request!

---

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

As the Christmas break is now finished it's time to get a new release out of the door!

This one introduces the following changes:

• Build Monitor is no longer affected by breaking UI changes introduced in Jenkins core 1.596:
  • the gear icon should not be cropped - thanks @mattjmorrison
  • Jenkins header and footer should stay hidden (#118)
• Job names are centered vertically and the progress bar correctly pulsates in Firefox (#95) - thanks @kriserickson
• Build Monitor supports LESS stylesheets, so adding any new UI changes should be simpler (ccab70b)

---

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

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!

---

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