On the topic of configuring workflow, curious to hear feedback on some ideas. I often hear that a "blank text area" is a bit intimidating, and of course docs and the snippet builder helps, but there can be more. Would people like to hear more about:
1) Richer content aware text/code editing (an editor that knows a bit about syntax, content assistance etc) - either on web or in an IDE? 2) Enhanced snippet builder that gives you a pallette of things to choose from 3) A more visual editor (last 2 are similar to what Gus showed if you watch his demo). I have been amused by google blockly (https://developers.google.com/blockly/?hl=en) enough to come up with a part of a block definition (attached example). While this looks odd, it is designed to be extensible and educational. Another approach (also attached) I have been experimenting with is a editable pipeline metaphor (this assume stages are the most visible elements as things move through a notional pipeline). Would love to talk more. On Thursday, September 24, 2015 at 3:18:07 AM UTC+10, Gus Reiber wrote: > > 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/44d99802-6b94-4652-85b7-5b372af4061b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
