For this article, I would like to review the different ways to report and chart with CloudBees Flow . Each has its pros and cons and not every solution is a perfect fit for your needs. We will look at the following:
- CI reports
- Standard reports and BIRT extension
- Unplug and HTML pages
- GWT pages
This is certainly the easiest way to add some charting to ElectricCommander and most of you should already be familiar with it. If not please consider attending one of our trainings. It gives you the ability to chart and keep track of values associated to your CI jobs very easily. In just a couple of clicks you can chart some job properties (user defined or intrinsic).
- Pros: Easy to set up.
- Cons: Not a lot of options for charting.
If you use the “Reports” sub-tab in your project, it will give you the opportunity to create more advanced reports like trends on ElectricCommander objects, pie charts, usage, … In addition, you can display those charts on your home page with a simple checkbox.
- Pros: A few more options.
- Cons: Limited to 5 series unless you want to go full steam ahead on BIRT report customization.
- Cons: A little slow at time. Hard to debug.
- Cons: the directory will be overwritten during update. Not “live” data.
When I started at CloudBees, it was pretty much the only option to display live data in some fancy way. I’ve never been a big fan due to my lack of skills with Java. I believe this is the best you can do for heavy UI. Java and its asynchronous requests will give you better performances and a more polish look. However it’s a more complex process, so complex in fact we offer its own full day of training around GWT and SDK.
- Pros: Faster, more polished UI and charting.
- Cons: Requires a full Java development environment. Complex
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.