+1, very exciting to make Jenkins operatable by newcomers in a matter of minutes. Having had very recently to drive a newbie to use Jenkins, even if he was very motivated, I think this is a great initiative. The flexibility of Jenkins is a great strength for advanced users, but a real difficulty for newcomers.
Though I agree using a watchdog tool like supervisord is not the official and best way to provide a Docker image, at the same time I agree this is a powerful way to make the experience very easy OOTB. I did that in the past for SonarQube, and it worked quite well for our usage. About supervisord specifically though, mostly a NIT/request for clarification: I wonder if the JEP should specify it? I read the reasoning <https://github.com/jenkinsci/jep/tree/master/jep/301#reasoning> and I understand this can save time and so on to start that work, but for instance if we discover a better alternative now or later, should a part of that JEP which somehow looks like an implementation detail (we mainly need to express we require a watchdog/restart tool don't we). Also/or this is typically a component that could be replaced later if something better surfaces or so? Also, adding another language dependency (python) when you already plan to have the evergreen client in nodejs might make the image bigger than it could be. But well, back to my previous point, this is something that can anyway be improved/changed over time. Thanks! 2018-02-06 17:02 GMT+01:00 R. Tyler Croy <[email protected]>: > > After pounding my head against my whiteboard for a couple months, I'm > finally > ready to talk about this idea which was first discussed at Jenkins World > 2017 > in San Francisco. > > At the Contributor Summit we held, Kohsuke challenged us to make Jenkins > easy > enough for an end-user to go from "zero" (downloading Jenkins) to > continuously > delivering a project in under 5 clicks and under 5 minutes. > > Jenkins Essentials has this goal in mind, with an additional goal of making > Jenkins development more efficient. > > I have proposed a draft of JEP-300 which outlines the problem domain and > overview of Jenkins Essentials more thoroughly > > rendered: https://github.com/rtyler/jep/tree/essentials-overview-300/j > ep/300 > pull request to jenkinsci/jep: https://github.com/jenkinsci/jep/pull/48 > > > To be successful with Jenkins Essentials, I'm endeavouring to improve > pre-release verification as well as post-release monitoring. Some of the > initial tasks that my colleague Raul and I are tackling can be found on > this > board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=396 > > > I'm still sketching out the Developer Experience aspects of this in another > thread once I have some thoughts written down. > > > Please take a look at the document and let me know what you think on this > thread :) > > > > Cheers > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > xmpp: [email protected] > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > ------------------------------------------------------ > > -- > 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/ms > gid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64% > 40blackberry.coupleofllamas.com. > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7hNzusookSN%2Btyw_ySc-d-7O_i%2Br9P8TcNBy2kx4UgZA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
