Thanks Kohsuke and Jenn for describing the plans for Blue Ocean. While I understand, that you all are moving away from long-lived road maps I think it still would make sense if you would clarify your vision for Blue Ocean and Jenkins (and the classic UI) in more detail.
Blue Ocean started three years ago with the vision to replace the whole UI, i.e. jenkins/job/pipeline configuration *and* the visualization of the job results. While I think we have a lot of exciting results for the former part (and JCaC for the configuratuion), the latter part has only results for less than 1% of the plugins. In "Jenkins: Shifting Gears“ Kohsuke also mentioned that the next development version of Jenkins will have no UI at all. This makes me somewhat uncertain about the future of the UI part in Jenkins. Are there still plans to replace the visualization of the job results of all plugins with Blue Ocean? Or wouldn’t it be easier to rework the classic UI by letting plugins use the old-style jelly model with some modern JS libraries like Bootstrap, JQuery, Datatables, ECharts, etc? Or thinking one step further: should we forget the Jenkins job visualization UI at all and plugin authors should create their own stand-alone UI (e.g. using a simple Spring Boot application) and read all information from the pluggable storage of a UI-less Jenkins using REST services? > Am 11.01.2019 um 19:04 schrieb Ryan <ryan.andrew.hendrick...@gmail.com>: > > I'm a big fan of Blue Ocean as well. I'd love to see more investment from > CouldBees to pushing Blue Ocean to it's limits. Glad to hear CloudBees is > still thinking about it. > > On Wednesday, December 12, 2018 at 3:30:10 PM UTC-5, Craig Rodrigues wrote: > Hi, > > When BlueOcean was originally being developed, James Dumay, > who was a Director, Product Management at Cloudbees > was very active in leading Blue Ocean, and communicating status and > milestones with the Jenkins community. > > Since James has left Cloudbees, what I have observed is: > > 1. No one at the manager/director level is visible on the > https://gitter.im/jenkinsci/blueocean-plugin > <https://gitter.im/jenkinsci/blueocean-plugin> Gitter channel to communicate > with users or get feedback > 2. Many bugs filed against Blue Ocean in JIRA are unassigned > 3. Cloudbees employees who log into > https://gitter.im/jenkinsci/blueocean-plugin > <https://gitter.im/jenkinsci/blueocean-plugin> seem to be doing so as a > best-effort/volunteer level. For example, on Nov. 16, Keith Zantow reported: > > Keith Zantow @kzantow Nov 16 06:36 @rodrigc hard to say exactly what's in the > road map at this moment, but certainly open to patches > > Can someone in Cloudbees management comment on the company's commitment to > Blue Ocean? > > I try to do what I can. I've submitted one bugfix: > https://github.com/jenkinsci/blueocean-plugin/pull/1794 > <https://github.com/jenkinsci/blueocean-plugin/pull/1794> > > And submitted a few bug reports: > https://bit.ly/2B8MmmQ <https://bit.ly/2B8MmmQ> > > Blue Ocean is very good, but needs some bugfixes and usability > fixes to meet parity with the Jenkins Classic UI. > Blue Ocean is some complicated "modern JavaScript", and I don't > have enough time to dig into it to fix the problems myself. > > I am trying to push Blue Ocean and Pipeline very heavily at the companies > I work for, and for the most part everyone I talk to really likes Blue Ocean, > but the bugs/gaps are a problem for wider adoption/success in the projects > I work on. > > Thanks for any feedback. > > -- > Craig > > > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/f10ccbbe-41ff-483f-a54d-bdebf2908670%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/f10ccbbe-41ff-483f-a54d-bdebf2908670%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5D2BC7B4-E303-4F9D-B127-092A76AF70A5%40gmail.com. For more options, visit https://groups.google.com/d/optout.
