Releases: jenkinsci/build-monitor-plugin
"Sorting By Status" fixed
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! 😄
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!
Optional culprits
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!
"How long has it been since the last build?"
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
Ordering by full name and a bugfix for Tomcat
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
Compatibility with Jenkins 1.596 and better support for Firefox
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
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!
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
Jenkins Logo
A minor release adding Jenkins logo to the Build Monitor view (#77) - thanks @bkmeneguello
Compatibility with Jenkins 1.574
This release addresses several backwards-incompatible changes introduced in the latest Jenkins Core:
- #79 - build number should correctly link to the build details page
- #75, #84 - Yahoo.Cookie library should be correctly loaded
There's also a small UI tweak:
- #67 - height of header and footer no longer depends on the size of the screen
and support for developing Build Monitor in Eclipse:
- #78 - .gitignore covers Eclipse-specific project files - thanks @bkmeneguello
Also, many thanks to @jglick for helping me with the investigation of #79 and raising JENKINS-24165.
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
Cleaner HTML
As @michaelneale rightly pointed out in #72, index.jelly not main.jelly should be used as the main page of Build Monitor. This change results in cleaner HTML DOM with no duplicate nodes.
Compatibility with Jenkins 1.572
Jenkins 1.572 introduced a re-written UI which required a slight tweak to the Build Monitor, so here it is - continuously delivered :-)