On Tuesday, May 27, 2014 7:41:10 AM UTC+10, Daniel Beck wrote:
>
>
> On 26.05.2014, at 21:08, Christopher Orr <ch...@orr.me.uk <javascript:>> 
> wrote: 
>
> > You often hear people say "the Jenkins UI is bad", but it's usually said 
> that there's a lack of concrete examples of *why* it's bad. 
>
> Wait, people complain but cannot provide concrete examples? Let me! 
>
> - Inserting a new 'first' build step above half a dozen existing ones is 
> really cumbersome. As is reordering build steps in general, as they tend to 
> be rather tall in some plugins. Hiding everything in Advanced sections by 
> default (see above) also doesn't help when it's a bunch of 30-50 line 
> scripts. 
>

Editing builds in freestyle builds is common - along with things like this 
- yet these are buried in the page as peers with things that you don't need 
to see 99% of the time (and can find when you need them). 
 

>
> - Since elements have no obvious borders (unless dragging, or hovering the 
> delete item), it's difficult to see where one element ends and another 
> starts (Conditional Build Step, I'm looking at you!) 
>

Ironically there are table borders on UI elements elsewhere, all over the 
place, usually where the visual cues are already there (ie executors, build 
lists etc - are obviously lists). I liked tom's grouping for starters. 
 

>
> ...
>
> - The first run experience is pretty weird if you look at it with some 
> Jenkins experience. It just dumps you onto an empty page telling you to 
> create a job, while only a completely different page shows a severe warning 
> (no security), and the global config requires changes (Jenkins URL, mail 
> server, ...) or otherwise things won't work right. 
>
>
Yes, I wonder if people would like some first-time jobs created (on demand, 
of course) - or would that just confuse people more as suddenly they have a 
bunch of artifacts they don't know what to do with? Some hints at the least 
could be nice, but most of us are far removed from first time experience it 
is hard to think back ;)

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to