On 30/05/2014 07:06, Michael Neale wrote:
It's a great point indeed and one of the main things I have learned from this thread i.e. move it forward incrementally + be very careful not to throw out the baby with the bathwater !!On Friday, May 30, 2014 2:51:15 AM UTC+10, Kevin Burke wrote: Second, I use Travis CI for building most of my Github projects, but one of my biggest frustrations with it is its occasional ability to pin a CPU, render a completely blank page, render nonsense, become unresponsive, etc. Travis CI is a single-page app. The failure modes of Javascript are legion, especially for people on flaky connections, and maybe not as well understood as the combination of HTML/CSS/occasional AJAX requests, for developers. *Jenkins' reliability in delivering a UI should be considered a core strength.*Never thought of that, but that is a good point. I suspect a parallel REST/SPA app will probably go on, but for now, I think this is a great (probably best) place to start?
I'd love to see us bring Kevin at al's Doony work back into Jenkins. If the community (and Kevin) were agreeable to that, I'd be more than happy to work on it. I guess we'd need to audit the changes made in Donny and work out any licensing issues if there are any.
-- 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.
