Responding (but obviously nothing official) but I like the points brought up by Craig and Uli.
To Ulis point: extensibility in GUI is haaard, and I don't think blue ocean has solved it to the point that those rich visual aspects of the 99% he alludes to can be catered to. There are some great ideas here - I liked the one of plugins thinking about visualisation specific to them (which may be able to be incorporated in many places). This plays into Kohsukes point "I think one key change in this space is that individualized feedback matters a lot more than it used to be" which I strongly agree with too. Eg people are looking at results right in pull requests, or slack messages and so on. To Craig's point - that is a great and fairly reasonable hitlist to make something end to end useful. On the first one I put a comment (not sure if pipeline jobs can be disabled at all...) but it is valid. The others are doable (the hard one is editing build info - as that is where extensible GUIs of plugins can kick in - but likely the scope can be contained here to be reasonable to make something useful end to end). That would be great! For the executors one - we could resurrect the old executor visualisation plugin (this was mostly done as a demo of extensibility, but perhaps it is time to fold it in) - there is some code here: https://github.com/jenkinsci/blueocean-executor-info-plugin which may be useful for that (doesn't need to be its own plugin, really...) On Saturday, January 19, 2019 at 5:08:48 PM UTC+11, Craig Rodrigues wrote: > > In my current job, we ely on the both the classic Jenkins UI and > the Blue Ocean UI very heavily. We have hundreds of tests, producing huge > log files. We use the test report viewer in classic UI and Blue Ocean > very heavily. > > Two things (out of many things) that I like about the Blue Ocean UI are: > > 1. massive text log files can be loaded more quickly in a web browser > 2. it is possible to hyperlink directly to a single line in a log file, > which is very useful for pasting > into an e-mail or a Slack message, to share with co-workers. > > I understand that the focus of Cloudbees has shifted to other things, and > maybe > for the next few years the pace of massive new work on Blue Ocean will be > slow. > However, it would still be nice to have someone (Cloudbees ?) fix some of > the minor > pot holes in Blue Ocean. For example: > > > - https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a > job in Blue Ocean > - https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does > not group changes for multiple SCM providers by SCM > - https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see > executors in Blue Ocean UI > - https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build > information in Blue ocean UI > > If some level of activity (even low level) could be invested in fixing > these types of pot holes, that would be nice. > If I am able, I will try to submit patches, but I'm a bit busy with my > job, and > am not an expert in Node.js. > > -- > Craig > > > On Thu, Jan 17, 2019 at 12:36 PM Kohsuke Kawaguchi <[email protected] > <javascript:>> wrote: > >> >> In a long run, I think UI is a crucial part of the value of Jenkins. >> It's what differentiated Jenkins from cron in the first place, and an >> important part of the continuous integration/delivery is to give visibility >> to more people, which to me necessarily includes consolidating information. >> > -- 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/27a3001c-8def-4329-a1ce-d7c6c921dee6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
