Re: Accelerating Jenkins development with Jenkins Essentials

Le 15 févr. 2018 21:29, "Baptiste Mathus" a écrit : +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

Re: Accelerating Jenkins development with Jenkins Essentials

+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 fo

Re: Accelerating Jenkins development with Jenkins Essentials

ok, starting to get your point. But then I wonder why you don't just get evergreen to be the process to start jenkins and control it as a child process, so you don't need extra supervisord 2018-02-14 21:06 GMT+01:00 R. Tyler Croy : > (replies inline) > > On Wed, 14 Feb 2018, nicolas de loof wrot

Re: Accelerating Jenkins development with Jenkins Essentials

(replies inline) On Wed, 14 Feb 2018, nicolas de loof wrote: > Something I don't get here is why you need an external evergreen-client to > manage updates, and can't just get this running from within Jenkins. This is covered under "Alternative Approaches" here: https://github.com/jenkinsci/

Re: Accelerating Jenkins development with Jenkins Essentials

Something I don't get here is why you need an external evergreen-client to manage updates, and can't just get this running from within Jenkins. I also wonder how you manage jenkins.war version here, which is bundled in the docker image vs upgrades. Does this mean the image comes with a default jen

Re: Accelerating Jenkins development with Jenkins Essentials

(replies inline) On Wed, 14 Feb 2018, nicolas de loof wrote: > > I haven't found any references to supervisord in JEP pull request, neither > about kubernetes - did I miss something ? > Anyway I tend to agree with this comment about packaging supervisord with > jenkins essential within a docker

Re: Accelerating Jenkins development with Jenkins Essentials

On Tue, Feb 13, 2018 at 7:04 PM, R. Tyler Croy wrote: > I think making a container > orchestrator a requirement at this point would only inhibit adoption and > learning. I am instead erring on the side of "simple and fast" from a user > perspective, the closest we can get (IMHO) to the `java -jar

Re: Accelerating Jenkins development with Jenkins Essentials

2018-02-14 1:04 GMT+01:00 R. Tyler Croy : > (replies inline) > > On Thu, 08 Feb 2018, Surya Gaddipati wrote: > > > Hi, > > > > This is exciting new development. > > > > Couple of comments > > > > 1. Packaging supervisord with another executable is a docker anti > pattern. > > I assume any seriou

Re: Accelerating Jenkins development with Jenkins Essentials

(replies inline) On Thu, 08 Feb 2018, Surya Gaddipati wrote: > Hi, > > This is exciting new development. > > Couple of comments > > 1. Packaging supervisord with another executable is a docker anti pattern. > I assume any serious jenkins deployment is on a scheduler like > swarm/kuberne

Re: Accelerating Jenkins development with Jenkins Essentials

While this thread is quiet, between the previous rounds of discussions in Jenkins World contributor summit and the recent mailing list discussion, I think there's a consensus of the general problem space. I intend to accept this JEP here within several day

Re: Accelerating Jenkins development with Jenkins Essentials

Yay! I think this is an important step for the Jenkins project. I'm really excited. We started talking about this in some of the events adjacent to FOSDEM. I think people generally grok the idea and they are happy that we are attacking these challenges. On Tue, Feb 6, 2018 at 8:03 AM R. Tyler Cro

Re: Accelerating Jenkins development with Jenkins Essentials

Hi, This is exciting new development. Couple of comments 1. Packaging supervisord with another executable is a docker anti pattern. I assume any serious jenkins deployment is on a scheduler like swarm/kubernetes ect where supervisord is not necessary. 2. Scripting should be done via yam

Accelerating Jenkins development with Jenkins Essentials

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" (dow