Wow. I am totally behind in responding to this thread. @Craig Rodrigues, I want to thank you for sending along some example of reporting visuals that you find helpful.
So far, I have been focused on the config end of the Jenkins user experience and not so much on the monitoring/reporting. I am hoping to shift that way soon, but sadly not today. Here is sketch video of some of my initial thoughts on reporting in Jenkins: http://youtu.be/J8AHhicq0_A Tangentially related to reporting, I have just completed a pair of workflow prototype videos: http://youtu.be/bEWsIP_r7-Y http://youtu.be/xbbIkAHUl7M ....the relation to reporting, is that I think that if Jenkins were to be a little more leading/prescriptive in how jobs should be assembled, it would a lot easier to aggregate interesting data. In building a GUI for Workflow construction, we have a chance to provide some of that guidance. Which in turn would allow for results presentations and groupings that are more independent of a folder structure. PS. I have a webinar tomorrow, so I am shamelessly hyping it: http://devops.com/2015/09/09/webinar-evolving-the-jenkins-ui/ Also, @gusreiber on Twitter, IRC and https://plus.google.com/+GusReiberUI/posts on Google+ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd8defe2-bd8d-4e74-b9e1-c8551f840369%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
