By claiming it. Build Monitor supports Jenkins Claim Plugin, so once you have it installed, enable "Broken build claiming" in the "Post-build actions" of your Jenkins job. From now on you'll be able to claim any further broken builds and Build Monitor will pick it up.
You might also be interested in a script that enables claiming on all your Jenkins jobs.
Wouldn't it be great to know what made your build fail? Well of course it would. Build Monitor supports Jenkins Build Failure Analyzer Plugin so get it, teach it and Build Monitor will tell you what the Failure Analyzer found out.
Install Jenkins Build Failure Analyzer Plugin and enable JUnit parsing in its configuration. This way failed test cases will be shown on the Build Monitor automatically.
Have a look at my article on "Communicating build status better".
You have several options here:
- review the granularity of your jobs: If you have too many low-level jobs displayed on one screen, consider consolidating them using Promoted Builds Plugin or MultiJob Plugin
- use job filters: Build Monitor supports Jenkins View Job Filters Plugin, if you have it installed
- if you've tried both the above options and still have two many jobs displayed - vote on #124. If there's interest in this feature - I'll get it implemented.
There's a colour blind mode you can enable in the Settings
If Jenkins runs behind a proxy, the problem is most likely in the proxy configuration. To fix an Apache proxy add the following line to the httpd.conf:
SetEnv force-proxy-request-1.0 1
More details in a comment on ticket #52 and on the apache website
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!
