Jenkins UX SIG Meeting Today

Hi, *Note: *This will be the last time I spam the Jenkins Developer group. If you are interested in the future of Jenkins UX please head over to the Jenkins User Experience mailing list <https://groups.google.com/forum/#!forum/jenkinsci-ux>. A quick reminder that the 2nd meeting

Re: Jenkins UX

Can someone please update this thread, the images are no longer there. https://jenkins.io/blog/2015/07/15/advancing-the-jenkins-gui-configuring-items-in-jenkins/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this gro

Re: Jenkins UX

Have you seen Blue Ocean? That's where most of the UX effort is happening right now. https://jenkins.io/blog/2016/05/26/introducing-blue-ocean/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop rece

Re: Jenkins UX

Any updates since 2015-06? Is this still an active effort? Or has the discussion/updates moved somewhere else? Thanks!! -- 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, sen

Re: Jenkins UX

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 (a

Re: Jenkins UX

Yes those are good clear visualisations. You mention writing dashboards, but I think to get a view like that it would effectively be a "dashboard" in the sense that it would have to take over the whole Jenkins UI to allow that much information to "radiate" out. Would be nice if people didn't nee

Re: Jenkins UX

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 h

Re: Jenkins UX

I noticed the config screen loaded/rendered even slower than I'm used see it in your demo, maybe it's just on your machine, but would it be possible to lazy/on demand load each section upon expansion and then start with just the first one expanded and all other collapsed? That could increase the re

Re: Jenkins UX

On 15.09.2015, at 21:25, Craig Rodrigues wrote: > With the stuff you are working on, would it be possible to generate reports > that > look like the waterfall in Buildbot? Something like: > > https://build.webkit.org/waterfall > http://build.chromium.org/p/chromium/waterfall > > These are no

Re: Jenkins UX

On Wed, Feb 18, 2015 at 8:27 AM, Gus Reiber wrote: > Again, if any of you all are at all interested in the Jenkins UX, we at > CloudBees are interested in helping move this ball forward and would love > to hear your feedback. > > > Two use cases that I use the Jenkin

Re: Jenkins UX

Daniel Beck: We already have something similar in the "context menu" for the 'configuration' bread crumb. Can't this be reused in some way? For the approach, I am pretty sure that is script scraping the page and appending DOM after the page renders, which we can do. But in terms of using some port

Re: Jenkins UX

One more question: will these changes have influence on existing plugins? How about back-compatibility? Thanks in advance. On Thursday, July 16, 2015 at 7:03:49 PM UTC+3, Gus Reiber wrote: > > As threatened, but at long last, I have a demo video and associated blog > post not really posted t

Re: Jenkins UX

Hello, Can I also insert my 5 cents(although I'm not a Jenkins contributor/committer). Idea with collapsable/expandable sections is great alone with floating list. But a lot of lines/margins break down jenkins minimalism, which I consider as a huge plus. So, something between current TC UI and c

Re: Jenkins UX

On 23.07.2015, at 00:52, Gus Reiber wrote: > So a ToC sort of display like Bootstrap's typically relies on a separate > rendering of the ToC from the actual content. > At the moment, this is nothing like the way the config page is currently > rendered. There are a number of ways to fix that. W

Re: Jenkins UX

eak it. > > Cheers > Bruno > > -- > *From:* Gus Reiber > > *To:* Jenkins Developers > > *Cc:* gre...@cloudbees.com > *Sent:* Thursday, July 23, 2015 10:31 AM > *Subject:* Re: Jenkins UX > > Awesome, awesome, awesome feedback all around.

Re: Jenkins UX

..back to specific bits of feedback here, there seems to be a lot of enthusiasm (including from me), about Daniel and Lucy's references to a Bootstrap pegged ToC style of navigation and section segmentation. I do have some concerns about that approach however, so I want to toss them out there t

Re: Jenkins UX

oving tables, divs, inputs, might break it. CheersBruno From: Gus Reiber To: Jenkins Developers Cc: grei...@cloudbees.com Sent: Thursday, July 23, 2015 10:31 AM Subject: Re: Jenkins UX Awesome, awesome, awesome feedback all around. So if I can summarize the feedback so far, it sounds

Re: Jenkins UX

Awesome, awesome, awesome feedback all around. So if I can summarize the feedback so far, it sounds to me like Kanstantsin is the most skeptical, but few if any of you are 100% sold, which is how it should be. Possible sources of discontent seem to break down like this: - Don't forget about

Re: Jenkins UX

https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin - looks a little bit ugly, but it close to what i mean. I mean sections like in travis, for each step out from the box четверг, 16 июля 2015 г., 19:03:49 UTC+3 пользователь Gus Reiber написал: > > As threatened, but a

Re: Jenkins UX

Plus ansi-color for color handling On Tuesday, July 21, 2015 at 3:11:47 PM UTC+3, Lucy Davies wrote: > > Looks like this one, right? > > https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin > > > -Lucy- > > On Tue, Jul 21, 2015 at 1:05 PM, Kanstantsin Shautsou < > kanstan

Re: Jenkins UX

Looks like this one, right? https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin -Lucy- On Tue, Jul 21, 2015 at 1:05 PM, Kanstantsin Shautsou < kanstantsin@gmail.com> wrote: > > On Jul 21, 2015, at 14:32, Kirill Merkushev wrote: > > Floating list with is good idea

Re: Jenkins UX

> On Jul 21, 2015, at 14:32, Kirill Merkushev wrote: > > Floating list with is good idea. > Scroll with mouse - can be done until your job is 50 screens long. Then you > dont want to scroll anymore :) > > Also it very useful for me to split console log for each invoked step and > make same fl

Re: Jenkins UX

Floating list with is good idea. Scroll with mouse - can be done until your job is 50 screens long. Then you dont want to scroll anymore :) Also it very useful for me to split console log for each invoked step and make same floating menu. четверг, 16 июля 2015 г., 19:03:49 UTC+3 пользователь Gu

Re: Jenkins UX

+1 for that style too! On Sat, Jul 18, 2015 at 4:54 PM Richard Bywater wrote: > +1 for that style. > > > On Sun, 19 Jul 2015 at 11:05 Daniel Beck wrote: > >> >> On 19.07.2015, at 00:55, Lucy Davies >> wrote: >> >> > Maybe have a tab bar, but which jumps you to a location on the current >> page

Re: Jenkins UX

+1 for that style. On Sun, 19 Jul 2015 at 11:05 Daniel Beck wrote: > > On 19.07.2015, at 00:55, Lucy Davies > wrote: > > > Maybe have a tab bar, but which jumps you to a location on the current > page, rather than switches you to a new page. > > I recently pointed Gus to this: > http://getboots

Re: Jenkins UX

Yeah, that's better than what I had in mind actually. -Lucy- On Sun, Jul 19, 2015 at 12:05 AM, Daniel Beck wrote: > > On 19.07.2015, at 00:55, Lucy Davies > wrote: > > > Maybe have a tab bar, but which jumps you to a location on the current > page, rather than switches you to a new page. > >

Re: Jenkins UX

On 19.07.2015, at 00:55, Lucy Davies wrote: > Maybe have a tab bar, but which jumps you to a location on the current page, > rather than switches you to a new page. I recently pointed Gus to this: http://getbootstrap.com/javascript/#js-overview Something like the list on the right would achi

Re: Jenkins UX

I have to agree that it's good to have them all on the same page. However, I do like the idea of being able to quickly navigate to a particular section with for example a tab bar. Maybe have a tab bar, but which jumps you to a location on the current page, rather than switches you to a new page

Re: Jenkins UX

-1 to tabs in my opinion. You spend a lot more time moving your mouse all around the screen going between the tab bar and the settings you are after. With them all on the same page then its easier to scroll to find the sections you are after with minimal mouse effort. (Let's not forgot those who ha

Re: Jenkins UX

Personally I like (some of) the proposed changes and the design looks like it would make things a lot easier to see what is going on. With respect to the example you've provided @ BuildHive, on my screen (MacOS Retina display) at least that looks like a real squashed mess of text where all the text

Re: Jenkins UX

Agree with Kostya. Its better than we already have, but no so useful as it may be. For example - job configuration page. You split every part to separate block. But it don't split user context completely. Why not to go deeper and split every part to separate tab. (As it done in TC or bamboo -

Re: Jenkins UX

Sorry, but for me this design is the way back to 90': huge margins, full of borders instead of current clean and clear UI (like https://buildhive.cloudbees.com/job/kohsuke/job/github-api/ ) . IMHO Many mentioned problems are caused by pure data forms and form bindings. You are demonstrating coll

Re: Jenkins UX

Hello Gus, looks great! Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Jul 16, 2015 at 6:03 PM, Gus Reiber wrote: > As threatened, but at long last, I have a demo video

Re: Jenkins UX

As threatened, but at long last, I have a demo video and associated blog post not really posted to a blog, but, still something that can be read and comment on Please take a look, and send feedback: video: http://youtu.be/1Qn4jEwAeGc post: https://docs.google.com/document/d/1sjd_Yl7wzyx

Re: Jenkins UX

Hey all, Been a long time since my last post, as I had been cramming getting a prototype built for JUCs DC and London. I am happy to report Tom and my presentation was well received in DC. Now we are off to the UK. Now that we have a simifunctional prototype, we will be working to figure out

Re: Jenkins UX

Hello Gus, The layout looks quite pleasing imo. I'm curious about the look-and-feel for the Workflow job-type. ;-) Anyway, I just would like to comment that the *sbt *logo you used there seems to come from a brazilian tv channel, not the "scala build tool". So, unless the idea is to build some

Re: Jenkins UX

Will this “UI”/“theme” be in separate plugin? > On Apr 23, 2015, at 16:27, Ullrich Hafner wrote: > >> >> Am 21.04.2015 um 22:09 schrieb Gus Reiber > >: >> >> Hey Daniel, >>Awesome feedback. You have pointed out a few things that I have totally >> missed and

Re: Jenkins UX

> Am 21.04.2015 um 22:09 schrieb Gus Reiber : > > Hey Daniel, >Awesome feedback. You have pointed out a few things that I have totally > missed and a few things that I have just not shown well with my wireframes. > So, let me see if I can work my way through your feedback: > Item selection

Re: Jenkins UX

Hello, Thanks a lot for looking into UI improvements. As a Jenkins job config admin, here are some comments about the current job build UI. Radio buttons are not dense enough, it wastes horizontal space and increases the vertical scrolling. For the collapsed and hidden items (e.g. those under

Re: Jenkins UX

If the collapsed/minimized form of the build step config was made pluggable (ex a collapsed.jelly next to config.jelly) the the readability of the overview could maybe be improved, for example a read only view of the first two lines of the execute shell step, the git url for the scm, the include pa

Re: Jenkins UX

On Tue, Apr 21, 2015 at 12:24 PM, Balder VC wrote: >> Perhaps it would be good to ask feedback from users on de user list, if >> you didn't already, I would assume they have a slightly different view >> then developers of Jenkins. On Tue, Apr 21, 2015 at 4:43 PM, Gus Reiber wrote: > I have not p

Re: Jenkins UX

Hey Tom, So for the most part, my screens are still in a pre style refinement stage and are just meant to convey particular layout concepts and not any particular art. ...that having been said... You are catching me starting to try to sneak some possible icon and typographic changes into my con

Re: Jenkins UX

Hey Balder, Thanks for the feedback. I have not posted to the de list, but I am eager to get quantity of feedback. Can you give me the URL to that list? I have to confess I am not familiar with it. I hear you about the big icons. In some respects it can look a bit like a kid drew the form inputs

Re: Jenkins UX

Hey Marius, Thanks for your awesome feedback. You express a concern about the delays of server round-trips, so before I take your comments in order, I want to say, I am envisioning these changes not actually requiring much functional change to the existing config/create form. Mostly these are DO

Re: Jenkins UX

Hey Daniel, Awesome feedback. You have pointed out a few things that I have totally missed and a few things that I have just not shown well with my wireframes. So, let me see if I can work my way through your feedback: - *Item selection page issues:* - *No descriptive text*: I very muc

Re: Jenkins UX

Hey Gus In general, I like the overhaul. But the big icon buttons are a bit overkill. The could be much smaller. And indeed as a long time jenkins user, I too am used to seeing all config at one sinlge glance but yes I sometimes still loose my may and spend some time looking ( ctrl+f ing ) for a s

Re: Jenkins UX

On 04/21/2015 06:08 PM, Daniel Beck wrote: > On 21.04.2015, at 13:52, Marius Gedminas wrote: > >> I'd love a "(?)" button somewhere near the bottom right corner of the >> text are, with a popup listing what environment variables I can use in >> the shell script. >> >> (Ideally plugins that defi

Re: Jenkins UX

On 21.04.2015, at 13:52, Marius Gedminas wrote: > I'd love a "(?)" button somewhere near the bottom right corner of the > text are, with a popup listing what environment variables I can use in > the shell script. > > (Ideally plugins that define new variables should be able to extend that > lis

Re: Jenkins UX

On Mon, Apr 20, 2015 at 02:41:07PM -0700, Gus Reiber wrote: >So I have let this thread go idle for over a month now, but over the > course of the last few weeks I have had some pretty interesting discussions > with both KK and Tom here inside CloudBees and now have some wireframes > that exa

Re: Jenkins UX

On 20.04.2015, at 23:41, Gus Reiber wrote: > As it stands today, most folks first interaction with Jenkins is a fairly dry > list of radio buttons, asking him/her to select which type of item to create. > Not only is the radio list fairly dry in appearance, as users add plugins it > does littl

Re: Jenkins UX

Hey Gus, these look really great and would be a huge step forward imo. I can see new users having a much easier/happier time with this ux. In terms of styling (colour, icons etc), what you have here is very different to what's in Jenkins atm. What's the plan there? On 20 April 2015 at 22:41, Gus

Re: Jenkins UX

Hey all, So I have let this thread go idle for over a month now, but over the course of the last few weeks I have had some pretty interesting discussions with both KK and Tom here inside CloudBees and now have some wireframes that examine the item creation and configuration GUI in jenkins and

Re: Jenkins UX

involved as a PHD thesis or as much as you have time >>> to type into a response box. >>> >>> To the extent that it helps conversation along, I also have a handful of >>> questions to which I would love responses: >>> >>> 1. For plugin builders,

Re: Jenkins UX

reate/config and >>the dashboard/job list grid, but would love to hear others and general >>feedback)? >>3. For UXers and other Jenkins contributors, how do my 3 forward >>paths seem (are there others, do you have experience with any yourself, do >>

Re: Jenkins UX

f canned options to >choose between? >5. Has anyone started using Workflow on a regular basis, and in >particular used the new workflow progress visualization enough to offer >feedback? > > > Again, if any of you all are at all interested in the Jenki

Re: Jenkins UX

On Saturday, February 21, 2015 at 6:08:12 PM UTC, Kanstantsin Shautsou wrote: > > @Tom, divs, css and tab it's cool, but as not UI developer i will expect > "building blocks" that will allow me just to use form and databinding. This > will also allow enhance/fix problems only in this block that

Re: Jenkins UX

Thanks Ioannis. On Saturday, February 21, 2015 at 5:09:27 PM UTC, Ioannis Moutsatsos wrote: > > I know that the fear of the unexpected consequences is always an issue. > However, given the benefits of improved an Configuration UI I think we > should be willing to take on some breaking changes. I

Re: Jenkins UX

l of plugin compatibility risk to see some improvement and > modernization in the Jenkins UX and an enhancement to the tool set that > allows for the construction of future UIs? > > > > > On Friday, February 20, 2015 at 3:57:28 PM UTC-8, Ullrich Hafner wrote: > As I plu

Re: Jenkins UX

cary)? >4. Has anyone tried to make their own themes with the new capabilities >Tom has added or would you appreciate and handful of canned options to >choose between? >5. Has anyone started using Workflow on a regular basis, and in >particular used the

Re: Jenkins UX

it sounds like you would be willing to accept some level of plugin compatibility risk to see some improvement and modernization in the Jenkins UX and an enhancement to the tool set that allows for the construction of future UIs? On Friday, February 20, 2015 at 3:57:28 PM UTC-8, Ullrich Hafne

Re: Jenkins UX

@Tom, divs, css and tab it's cool, but as not UI developer i will expect "building blocks" that will allow me just to use form and databinding. This will also allow enhance/fix problems only in this block that will automatically apply to other places. More thoughts. - I think that other UI pro

Re: Jenkins UX

Yes, I think everyone agrees that the config pages are a UX nightmare. We looked at changing how they are rendered by introducing sections that are then collapsible. It was somewhat of a success but what frightened me off taking it further was the fact that it was inevitably going to break plu

Re: Jenkins UX

have experience with any yourself, do any >seem scary)? >4. Has anyone tried to make their own themes with the new capabilities >Tom has added or would you appreciate and handful of canned options to >choose between? >5. Has anyone started using Workflow on a regular basis

Re: Jenkins UX

new capabilities Tom has > added or would you appreciate and handful of canned options to choose between? > Has anyone started using Workflow on a regular basis, and in particular used > the new workflow progress visualization enough to offer feedback? > > Again, if any of you all

Re: Jenkins UX

Great stuff here guys. Hopefully we can translate some of these ideas into here into JIRA feature tasks (if not already in JIRA) for tracking (label "user-experience"). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Jenkins UX

: Gus Reiber To: jenkinsci-dev@googlegroups.com Sent: Wednesday, February 18, 2015 6:05 PM Subject: Re: Jenkins UX Thanks for your feedback, Bruno.Your concern is exactly the concern that keeps me up at night. Thanks also for raising Uno Choice as an example.I am very much looking for specific exa

Re: Jenkins UX

;>>1. For plugin builders, can you tell me a bit about creating the UI >>>portion of your plugin (did you use the data binding form controls, what >>>was hard, what did you have to invent)? >>>2. For regular Jenkins users, what are the UX areas of

Re: Jenkins UX

arrive at home. ThanksBruno From: Gus Reiber To: jenkinsci-dev@googlegroups.com Sent: Wednesday, February 18, 2015 6:05 PM Subject: Re: Jenkins UX Thanks for your feedback, Bruno.Your concern is exactly the concern that keeps me up at night. Thanks also for raising Uno Choice as an

Re: Jenkins UX

love to hear others and general >>feedback)? >>3. For UXers and other Jenkins contributors, how do my 3 forward >>paths seem (are there others, do you have experience with any yourself, do >>any seem scary)? >>4. Has anyone tried to make their own th

Re: Jenkins UX

ould most like to see improved (I think it is the item create/config and >>the dashboard/job list grid, but would love to hear others and general >>feedback)? >>3. For UXers and other Jenkins contributors, how do my 3 forward >>paths seem (are there other

Re: Jenkins UX

internally Jenkins controls the selectors to access the parameters. > Should any of these changes, plug-ins wouldn't be affected. > ``` > > Not sure if that's the best option... > > My +1 :^) please continue the hard work on improving Jenkins UX. > > All the best, &g

Re: Jenkins UX

ne tried to make their own themes with the new capabilities >Tom has added or would you appreciate and handful of canned options to >choose between? >5. Has anyone started using Workflow on a regular basis, and in >particular used the new workflow progress visualiz

Re: Jenkins UX

, do any >seem scary)? >4. Has anyone tried to make their own themes with the new capabilities >Tom has added or would you appreciate and handful of canned options to >choose between? >5. Has anyone started using Workflow on a regular basis, and in >

Re: Jenkins UX

anyone tried to make their own themes with the new capabilities >Tom has added or would you appreciate and handful of canned options to >choose between? >5. Has anyone started using Workflow on a regular basis, and in >particular used the new workflow progress vis

Re: Jenkins UX

`` Not sure if that's the best option... My +1 :^) please continue the hard work on improving Jenkins UX. All the best, Bruno From: Gus Reiber To: jenkinsci-dev@googlegroups.com Sent: Wednesday, February 18, 2015 2:27 PM Subject: Jenkins UX At the end of last summer, my frie

Jenkins UX

between? 5. Has anyone started using Workflow on a regular basis, and in particular used the new workflow progress visualization enough to offer feedback? Again, if any of you all are at all interested in the Jenkins UX, we at CloudBees are interested in helping move this ball forwa