On Tuesday, May 27, 2014 7:29:54 AM UTC+1, Dominik Bartholdi wrote: > > Glad to see others coming up with this topic again! > We have talked about this on many occasions and some work has been done in > a separate branch too: > https://github.com/jenkinsci/jenkins/tree/ui-changes > In JIRA we also created a special component (ui-changes) to keep track of > all this: > https://issues.jenkins-ci.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+Jenkins+and+component+%3D+ui-changes&runQuery=true&clear=true > …but unfortunate all/most the effort which was put into any attempts of > changing the UI of Jenkins has stopped at some point. I think the biggest > problem really is to find a common agreement on anything - there is always > someone who does not like it. >
I think there are quite a few technical "barriers" to making meaningful change the UI too. This is inevitable, given the size and success of Jenkins. > Although I agree, the current implementation does its job and most of the > people get a long with (maybe just because they have not seen anything else > yet) - I absolutely think the look and feel is way off what a user can/does > expect nowadays. In fact I know of a couple of teams which have chosen an > other CI server then Jenkins just because of the UI (e.g. TeamCity) - I > also think Jenkins has by far more capabilities then e.g. TeamCity, but not > everyone needs the more advanced plugins/features/extensionpoints and these > users can happily choose a nicer looking CI server (I would too). > +1 > > Also the fact that there are so many different approaches on changing the > UI tells me that there is something we should improve. > Some more examples > - https://github.com/rackerlabs/canon-jenkins > - https://github.com/djonsson/jenkins-atlassian-theme -> > http://test.do/(making Jenkins look like bamboo) > - > http://isotope11.com/blog/styling-your-jenkins-continuous-integration-server > ... > > As a reference, there are also the notes we made about the discussions we > had at another FOSDEM: > https://wiki.jenkins-ci.org/display/JENKINS/UI+Enhancements > Great stuff... thanks Domi. > > Domi > > > On 27.05.2014, at 05:10, Michael Neale <[email protected] <javascript:>> > wrote: > > > > On Tuesday, May 27, 2014 5:08:28 AM UTC+10, Christopher wrote: >> >> >> >> But having seen a colleague of mine use the Jenkins API and AngularJS to >> build some really nice (though narrowly focussed) Jenkins front-ends for >> internal apps, dashboards and for customer use, I really like the idea >> of building the Jenkins UI on top of its API. >> >> As you may have seen, this is something Tyler did some work on during >> FOSDEM last year. The basic prototype I saw at the time was pretty >> decent, but as mentioned above and at the time, of course there's a >> *lot* of backward- and plugin-compatibility to think about: >> https://groups.google.com/forum/#!topic/jenkinsci-dev/dV680PGiI1Y >> >> >> I have some experience doing fairly advanced UIs on top of the various > APIs - they are quite powerful (other than, notably the config - where it > is more of an xml blob) for doing a lot of things. This does feel a little > "boil the ocean", and even if worthwhile, the non js based UI will be > around for a long time yet, so it is probably worth putting a bit if work > in to that to start with. > > > -- > 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] <javascript:>. > For more options, visit 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
