Re: Coding a new type of agent

[Carlos Sanchez]

It's been a while but I believe that for the declarative agent
definition you need something like KubernetesDeclarativeAgent [1] In
that dir you can find the other declarative pipeline code

I would not bring all the options from the k8s plugin as it has a lot
of accumulated cruft. You can do with just the declarative pipeline
options and yaml definitions without needing UI setup as it the k8s
plugin was initially implemented

If you want to look at the very basics of the plugin implementation
with declarative pipeline support you can back in history to [2]

[1] 
https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/KubernetesDeclarativeAgent.java
[2] 
https://github.com/jenkinsci/kubernetes-plugin/tree/c12cb70b3118079b1054b4579eedc326c0e09ac7/src/main/java/org/csanchez/jenkins/plugins/kubernetes


On Thu, May 16, 2024 at 4:41 PM Ivan Pavlović  wrote:
>
> Hi all,
>
> I have been looking into the kubernetes plugin for jenkins as an inspiration 
> for my own plugin i would like to write. This plugin should provide a new 
> type of agent that can be used in the declarative pipeline. Also, it would 
> need to provide users an option to create a new type of cloud.
>
> So far, i have been able to implement all that is needed for a new type of 
> cloud, but i can't seem to figure out what would be extension points to 
> provide a new type of agent.
>
> If you wonder why i am using kubernetes plugin for Jenkins as an inspiration, 
> it's because this new agent will communicate with an open source batch job 
> scheduler called Armada. Armada operates on top of k8s clusters, and it 
> receives a yaml manifest that it interprets and knows how to communicate with 
> k8s API to deploy pods and schedule jobs. So i don't need to integrate with 
> k8s API directly.
>
> Example like this, taken from the homepage of kubernetes plugin:
> ```
> pipeline {
>   agent {
> kubernetes {
>   yaml '''
> apiVersion: v1
> kind: Pod
> metadata:
>   labels:
> some-label: some-label-value
> spec:
>   containers:
>   - name: maven
> image: maven:alpine
> command:
> - cat
> tty: true
>   - name: busybox
> image: busybox
> command:
> - cat
> tty: true
> '''
>   retries 2
> }
>   }
>   stages {
> stage('Run maven') {
>   steps {
> container('maven') {
>   sh 'mvn -version'
> }
> container('busybox') {
>   sh '/bin/busybox'
> }
>   }
> }
>   }
> }
> ```
>
> should now be:
> ```
> pipeline {
>   agent {
> armada {
>   yaml '''
> ...
> '''
>   retries 2
> }
>   }
>   stages {
> 
>   }
> }
> ```
>
> Can you help me out in implementing something like this?
>
> Thanks!
>
> Best regards,
> Ivan

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6P_FBySnTV7M9WhLbDhsCEVCMPd3e5ax80-hH52veofzw%40mail.gmail.com.

Re: default container in Kubernetes plugin

[Carlos Sanchez]

Hi, as Jesse mentioned in jira it is not possible because the plugin is not
called unless the pipeline explicitly uses a kubernetes agent


On Thu, Mar 18, 2021, 01:16 Daniel Ferreira  wrote:

> Hello, the ticket is already created here:
> https://issues.jenkins.io/browse/JENKINS-64778
>
> I want to implement it, but need some guidance and ideas ... please :)
>
> After some debugging and reading the code, I found that, when calling
> the plugin using label like "agent { label 'ubuntu-18-04' } ", I cannot
> reuse
> the existing "defaultContainer" feature that is available when calling
> "agent { kubernetes { ... } } " -- because the implementation fully
> depends on that
> "kubernetes agent" being called.
>
> Instead I was thinking that maybe I need to catch the "steps" calls on
> each stage and wrap them in a "ContainerStep" call. But, first, I don't
> know if that's possible or how to do it. And, second, this seems like a
> huge amount of changes for such a, theoretical, simple feature.
>
> Does anyone has a good idea on how to implement this?
>
> Thanks
>
> A terça-feira, 21 de agosto de 2018 à(s) 12:57:00 UTC+1, car...@apache.org
> escreveu:
>
>> You can submit a PR. Opening a ticket won't help much as I won't have
>> time to implement it
>>
>> On Tue, Aug 21, 2018, 12:59 arch  wrote:
>>
>>> ok, do I need create a ticket in
>>> https://issues.jenkins-ci.org/secure/Dashboard.jspa first?
>>>
>>> On Tue, Aug 21, 2018 at 6:57 PM Carlos Sanchez 
>>> wrote:
>>>
>>>> sounds good to me
>>>>
>>>> On Tue, Aug 21, 2018 at 12:38 PM arch  wrote:
>>>>
>>>>> Yes, I get your point. So I suggest offer a UI option, and let end
>>>>> users make choice.
>>>>>
>>>>> On Tue, Aug 21, 2018 at 6:34 PM Carlos Sanchez 
>>>>> wrote:
>>>>>
>>>>>> the problem is how to know when you want a container be a default,
>>>>>> you would need to pass it as an option in the pod template definition
>>>>>>
>>>>>> On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:
>>>>>>
>>>>>>> When I configure a pod template with java container. Then run a
>>>>>>> shell script in pipeline, it will cause an error that can't find command
>>>>>>> java. So I must specify the container as java first.
>>>>>>> I suggest that the java container should be the default container
>>>>>>> instead of jnlp. Any feedback is thankful, welcome to discuss.
>>>>>>>
>>>>>>> --
>>>>>>> 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-de...@googlegroups.com.
>>>>>>> To view this discussion on the web visit
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>> .
>>>>>>> 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 jenkinsci-de...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>> 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
>>>>> a

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

[Carlos Sanchez]

LGTM

On Tue, Dec 10, 2019 at 7:51 PM Slide  wrote:

> +1 looks like a great idea!
>
> On Tue, Dec 10, 2019 at 8:38 AM Matt Sicker  wrote:
>
>> +1 to this idea and initial maintainers. This would go a long way
>> toward unblocking changes in this area! :)
>>
>> On Tue, Dec 10, 2019 at 7:42 AM Marky Jackson 
>> wrote:
>> >
>> > I have not been as active as I would like but I would also like to be a
>> maintainer based on our previous conversation
>> >
>> > On Dec 10, 2019, at 3:34 AM, Oleg Nenashev 
>> wrote:
>> >
>> > 
>> > BTW, I suggest the following list of maintainers based on the recent
>> activity:
>> >
>> > Mark Waite
>> > Alex Earl
>> > Carlos Sanchez
>> > Oleg Nenashev
>> > Baptiste Mathus
>> > Olivier Vernin
>> >
>> > Alternative is to just keep all members of
>> https://github.com/orgs/jenkinsci/teams/docker/members though some
>> contributors are not active at the moment
>> >
>> > BR, Oleg
>> >
>> > On Tuesday, December 10, 2019 at 11:42:49 AM UTC+1, Mark Waite wrote:
>> >>
>> >> I would like that very much
>> >>
>> >> On Tue, Dec 10, 2019, 11:19 AM Oleg Nenashev 
>> wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> Right now we have a number of official packages for Docker:
>> >>>
>> >>> https://github.com/jenkinsci/docker
>> >>> https://github.com/jenkinsci/docker-slave
>> >>> https://github.com/jenkinsci/docker-ssh-slave
>> >>> https://github.com/jenkinsci/docker-jnlp-slave
>> >>> https://github.com/jenkinsci/jnlp-agents
>> >>>
>> >>> All these repositories have different teams which define
>> permissions/. In addition to that we have jenkinsci/docker and
>> jenkinsci/docker-packaging-team team which also grant permissions. It is
>> quite difficult to manage the repositories in the current state, and it is
>> difficult to request reviews.
>> >>>
>> >>> I suggest to keep things simple and just proceed with a single team
>> for the official packaging:
>> >>>
>> >>> Introduce an official "docker-packaging-team" under umbrella of
>> Platform Special Interest group which currently manages Docker packaging
>> >>> Cleanup existing teams, leave just one for all official Jenkins
>> master and agent mages. Plugin Docker packaging (e.g. Remoting over Apache
>> Kafka, Swarm plugin) will not be affected
>> >>> Update GitHub and DockerHub teams to reflect the changes (mostly
>> jenkins4eval which grants write permissions)
>> >>> Add new team to CODEOWNERS in all repos
>> >>>
>> >>> WDYT?
>> >>>
>> >>> Thanks in advance,
>> >>> Oleg
>> >>>
>> >>> --
>> >>> 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 jenkin...@googlegroups.com.
>> >>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPBvAvsqC4nqpr2e%2BqBOo2BdMqa%3DY5%3Dx%2BhVO735YzX_w%40mail.gmail.com
>> .
>> >
>> > --
>> > 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.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/d333d077-28bb-431f-9f5a-950440970429%40googlegroups.com
>> .
>> >
>> > --
>> > 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.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/11566D48-9955-40F5-B5EA-75CAEB228589%40gmail.com
>> .
>>
>>
>>
>> --
>> Matt Sicker
>> Senior Software Engineer, CloudBees
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsub

Upcoming changes to docker official java images

[Carlos Sanchez]

https://github.com/docker-library/openjdk/pull/322

I don't have the time right now to go through the implications for the
jenkins images, so if someone wants to take a look

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6O6xK4NECYr182B5RU2B5VneN4xEF0dp5gh2XFO_mpi%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Automating dependency management for repositories inside the jenkinsci org

[Carlos Sanchez]

please add https://github.com/jenkinsci/kubernetes-plugin

thanks

On Wed, Mar 27, 2019 at 5:33 PM Jesse Glick  wrote:

> Please remove `pipeline-cloudwatch-logs-plugin` since its interesting
> tests are not currently run in CI.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3%2BA%3DuSo4kmOM_BXjbOVeN9u9UFUChB59csZGhW7AoPgA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OAy5HHW_aDNp-xCv69zxvW7p05VCdXh9LjVte%3DOpRhjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins official kubernetes operator

[Carlos Sanchez]

I'll be sending a note to the group soon to close the dates
https://groups.google.com/forum/#!forum/jenkins-cloud-native-sig

On Fri, Feb 15, 2019 at 4:35 PM Tomasz Sęk  wrote:

>
> Hi Carlos,
>
> I can introduce operator at the next Cloud Native SIG meeting. Cloud you
> provide more information about meeting itself(agenda, video link etc.)?
>
> Regards,
> Tomasz
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a2fd940c-f5ce-4928-b244-4e976d5e183c%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6M6ja8LVjtcwLCqR%3D5Y%3DpviOGAGX_hUgwFWimuKxwitdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins official kubernetes operator

[Carlos Sanchez]

Would Tomasz or anyone else working on the operator like to introduce it at
the next Cloud Native SIG meeting the week of February 25th?


On Thu, Feb 14, 2019 at 7:35 AM Oleg Nenashev 
wrote:

> Hi Tomasz,
>
> Before I proceed with this request, would you like to start from an
> Experimental DocherHub organization?
> https://github.com/jenkinsci/jep/tree/master/jep/217
>
> BR, Oleg
>
> On Wednesday, February 13, 2019 at 9:03:08 PM UTC+1, Tomasz Sęk wrote:
>>
>>
>> Hi all,
>>
>> I've raised ticket INFRA-2013
>>  for Docker Hub
>> repository.
>>
>> Regards,
>> Tomasz
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/f3f55c14-8197-4ec0-8963-27c6301e7d24%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Oq%2BXdswtSDWMAsww%3DrbnZTpu29jRM2zTGccdoZxw2Ozg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to override the port properties when running the JenkinsRule?

[Carlos Sanchez]

is it the port or the ip? I've seen that error when it tried to bind to an
ip address that did not exist


On Wed, Jan 30, 2019 at 9:10 PM Victor Martinez <
victormartinezru...@gmail.com> wrote:

> Hi guys,
>
> I'm running out of ideas. I'm getting some binding errors when running the
> tests for the jenkins core locally. Probably that's something I can easily
> fix by setting the port, but I've no clue where I can find those details,
> even though I already with  mvn -Pdebug  verify -Dport=18080  but it
> didn't work (as I saw the property in the source code: (
> https://github.com/jenkinsci/jenkins-test-harness/blob/6d9d823fffcfac02303a4d330e2ddab9553fe9ac/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L693
> )
>
> See the below stacktrace for the record:
>
> java.net.BindException: Can't assign requested address
>
>at sun.nio.ch.Net.bind0(Native Method)
>
>at sun.nio.ch.Net.bind(Net.java:433)
>
>at sun.nio.ch.Net.bind(Net.java:425)
>
>at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>
>at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>
>at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:298)
>
>at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
>
>at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
>
>at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>
>at org.eclipse.jetty.server.Server.doStart(Server.java:431)
>
>at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>
>at
> org.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:693)
>
>at
> org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:619)
>
>at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:391)
>
>at
> org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:544)
>
> Any ideas what's going on and how I can set the port for my running tests?
>
> Thanks
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/58d3a6b2-2ea0-41a3-bd53-2b3058e5b744%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6P3s7QR%2Bc8z%2BAMe_mU0snBk47mgKPqgKyJsCeQWs-o-HA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Running Jenkins Pipelines in AWS Lambda

[Carlos Sanchez]

In case anyone is interested I created a PoC to run jenkinsfile-runner in
AWS Lambda for a totally serverless execution.

https://github.com/carlossg/jenkinsfile-runner-lambda
https://blog.csanchez.org/2019/01/29/running-jenkins-pipelines-in-aws-lambda/

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OPrWYM1%2BsAkEEc2rG%3DBRaGs409OCDFcLa%3DB79FODw%2BtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: A new home for Jenkins

[Carlos Sanchez]

Great news for the community!
Thanks KK

On Wed, Jan 16, 2019 at 7:58 PM Kohsuke Kawaguchi  wrote:

> Ever since our project got our present ‘Jenkins’ name in 2011, we’ve
> always been conscious about the governance of this project. It’s a key part
> of ensuring the well-being of the project. We’ve not only talked the talk,
> but done some walking the walk too, such as team
> , JEP
> , and SIG .
>
> One idea in this space that we’ve discussed in and out is software
> foundation around Jenkins. Those of you who came to Jenkins World
> Contributor Summit in 2017 might remember Tyler presenting this idea under
> the name “Jenkins Software Foundation” (see slides
> 
> and notes
> ),
> at the DevOps World | Jenkins World Contributor Summit in 2018 and
> afterwards, Tracy has helped continue this conversation (see slides
> 
> ).
>
>
> *Why?*
> In a nutshell, the “problems” we are trying to solve here are:
>
>
>- *Limits to current support and services* - Software in the Public
>Interest , which currently hosts Jenkins, is a
>fairly modest “limited service” non-profit organization. I love what they
>do, but we could use more help; entering into legal contracts, setting up
>recurring payment that doesn’t go through my own personal credit card.
>These inabilities hamper the growth of the project.
>
>- *High barrier to participation by corporate contributors* - Our
>unique governance structure makes it unnecessarily hard for corporate
>contributors to come in and feel at home. We aren’t an Apache project, an
>Eclipse project, nor a company-owned project like Chef or Spring. We are
>just a little too unique to be understood by corporate open-source offices,
>lawyers, and pointy-haired bosses. The net result is that we lose out on
>their participation and contributions — money and people. I’ve been on the
>phone with some of those companies myself, and so has Tracy.
>
>- *Misperception that Jenkins is owned by CloudBees* - A common
>perception error is that Jenkins is a CloudBees project, when it really
>isn’t. But this perception is self-perpetuating. We want a long-term
>structure to keep Jenkins alive and thriving, and not being tied to the
>fate of any single entity is a key requirement. We want more companies to
>participate in Jenkins, feel a co-ownership, and push Jenkins forward
>together.
>
>- *Need to coordinated broader community of contributors* - On the
>people front, it used to be that the bulk of the forward motion in this
>project came from individual plugin developers. Today, where we need to
>move forward requires more organized contributors and skills other than
>coding. Blue Ocean was a good example. So was Config as Code, where it took
>the persistence of two corporate contributors. Pipeline Authoring SIG
> to me is another young
>example where if you look at the key participants, it really represents
>organizations and what they are concerned about.
>
>- *Raising and using money well* - On the money front, we are not
>tapping our ability to raise money, and we lack the ability to use it
>effectively. On the few
>
>occasions
>
>that we did a donation drive, we have shown incredible ability to raise
>money, but I know we can do a few orders of magnitude more. Plus, this kind
>of irregular income is difficult to make the most of, because it’s hard to
>enter into recurring expenses. Also, without our own legal entity, we lack
>the ability to turn the money into what’s most precious — people!
>
> Given all this, the Jenkins board, CloudBees (as the biggest contributor),
> and the Linux Foundation kept exploring this foundation idea beyond those
> contributor summits. We have floated some ideas with some of the companies
> participating in the ecosystem. Thoughts have evolved, ideas turned into
> more concrete plans, and I think it has developed to a point where this is
> beginning to look real, and really makes a lot of sense for the project.
>
>
> *What?*
> So here are the key ideas/features of the foundation:
>
>
>- We are calling it “Continuous Delivery Foundation” (CDF), and it
>will have a broader charter. It will house not just Jenkins but other
>open-source projects in this space. Through the CDF, 

Re: jenkins official kubernetes operator

[Carlos Sanchez]

I thought about it, and yes it would be interesting to have an operator
that watches a configmap and ensures jenkins is always updated.
However with serverless jenkins[1] you wouldn't need to worry about that
anymore (if you can use serverless).


[1]
https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870

On Tue, Jan 15, 2019 at 6:37 AM 夏润泽  wrote:

> Hi dev:
>In the cloud native domain, kubernetes is an important part, and now
> many software are using kubernetes operator to manage applications in
> kubernetes.
>Now we can manage jenkins through groovy scripts, casc plugins, etc.In
> particular, the casc plugin allows us to manage jenkins with declarative
> code.
>But I think there are still some problems in it. I deployed my jenkins
> in the kubernetes cluster and managed my jenkins through the groovy script
> and the casc plugin. But once the jenkins is started, I need to modify the
> configuration of the casc, then I need to submit the configuration to the
> jenkins dashborad, and the submitted configuration is not necessarily
> successful, and there is no failure record. In other words, although I have
> a casc configuration file, it is difficult for me to ensure that my
> environment is consistent with the casc configuration. Or at least let me
> know that my current configuration is incorrect, I need to fix it.
>If we can provide an official jenkins operator to manage jenkins in
> kubernetes, it must be great.
>I hope to hear your opinions.
>
> Best wishes
> RunzeXia
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: kubernetes-plugin could use Jobs instead of bare Pods

[Carlos Sanchez]

On Mon, Nov 26, 2018 at 10:08 AM Olblak  wrote:

> Note that I don't think it would fix a) as Jenkins expects the agent to
> keep state. ie. agent clones git repo then crashes later on, Jenkins
> expects the agent to already have the gi repo cloned after agent restart
>
>
> Why not using persistent volume to keep the state? Like an emptyDir?
>

if pod terminates emptyDir is no longer available. And using a persistent
volume like block storage brings other problems like attachments,
rescheduling in different AZs,...


>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
>
>
> On Thu, Nov 22, 2018, at 5:49 PM, daniel.schiem...@gebit.de wrote:
>
> Nice, I will start off your master then.
>
> And yes, a) might actually not be fixed by using Jobs. I will continue
> researching and report back.
>
> Regards,
> Daniel
>
> Am Donnerstag, 22. November 2018 16:42:04 UTC+1 schrieb Carlos Sanchez:
>
> It's not using jobs because they did not exist when the plugin was
> created, and yes, it would be a good addition to the plugin.
>
> Note that I don't think it would fix a) as Jenkins expects the agent to
> keep state. ie. agent clones git repo then crashes later on, Jenkins
> expects the agent to already have the gi repo cloned after agent restart
>
>
> On Thu, Nov 22, 2018 at 4:04 PM  wrote:
>
> Hi all,
>
> I am working on a kubernetes cluster for Jenkins. I quickly found Carlos
> Sanchez' kubernetes-plugin and started using and adapting it.
> The plugin creates "bare" Pods directly in kubernetes, watches and in the
> end deletes them after the agent process inside the Pod terminated.
> I think there are several issues with this:
> a) bare Pods do not get rescheduled in failover cases, for example node
> crash
> b) kubernetes-plugin is responsible for deleting such a bare Pod (because
> Pods are designed to never terminate). If Jenkins (or the node its running
> on)
> crashes while terminating the slave, it might never actually delete the
> Pod.
> c) kubernetes-plugin immediately deletes the Pod after the build inside
> the container is finished. If something else is happening inside the Pod
> after
> the build (e. g. cleanup or syncing), it has no chance of completing.
>
> While researching, I found out that kubernetes provides a "Job" object
> that runs a certain amount of containers until successful completion.
> Using a kubernetes Job to schedule builds onto the cluster seems to solve
> all my aforementioned issues.
> a) a Job ensures that the specified number of completed runs are achieved,
> even in case of failover
> b) and c) a Job automatically deletes all associated Pods when it gets
> deleted (and finished Jobs themselves can get auto-deleted with
> the new alpha feature TTLAfterFinished in k8s v1.12). This frees the
> kubernetes-plugin from caring for the Pods after build completion.
>
> Has anyone experience with kubernetes Jobs? Am I missing something obvious?
>
> @Carlos Sanchez: If not, I would try to implement this in your
> kubernetes-plugin. Would you be interested to get this back into your
> mainline? Then I would fork the github repo and start directly off master.
>
> Regards,
> Daniel
>
>
> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/1fe306b4-f8f6-48b1-a98a-087b119f880f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1fe306b4-f8f6-48b1-a98a-087b119f880f%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/25d96a14-4d8d-407d-aa21-ead2188b08af%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/25d96a14-4d8d-407d-aa21-ead2188b08af%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.

Re: kubernetes-plugin could use Jobs instead of bare Pods

[Carlos Sanchez]

It's not using jobs because they did not exist when the plugin was created,
and yes, it would be a good addition to the plugin.

Note that I don't think it would fix a) as Jenkins expects the agent to
keep state. ie. agent clones git repo then crashes later on, Jenkins
expects the agent to already have the gi repo cloned after agent restart


On Thu, Nov 22, 2018 at 4:04 PM  wrote:

> Hi all,
>
> I am working on a kubernetes cluster for Jenkins. I quickly found Carlos
> Sanchez' kubernetes-plugin and started using and adapting it.
> The plugin creates "bare" Pods directly in kubernetes, watches and in the
> end deletes them after the agent process inside the Pod terminated.
> I think there are several issues with this:
> a) bare Pods do not get rescheduled in failover cases, for example node
> crash
> b) kubernetes-plugin is responsible for deleting such a bare Pod (because
> Pods are designed to never terminate). If Jenkins (or the node its running
> on)
> crashes while terminating the slave, it might never actually delete the
> Pod.
> c) kubernetes-plugin immediately deletes the Pod after the build inside
> the container is finished. If something else is happening inside the Pod
> after
> the build (e. g. cleanup or syncing), it has no chance of completing.
>
> While researching, I found out that kubernetes provides a "Job" object
> that runs a certain amount of containers until successful completion.
> Using a kubernetes Job to schedule builds onto the cluster seems to solve
> all my aforementioned issues.
> a) a Job ensures that the specified number of completed runs are achieved,
> even in case of failover
> b) and c) a Job automatically deletes all associated Pods when it gets
> deleted (and finished Jobs themselves can get auto-deleted with
> the new alpha feature TTLAfterFinished in k8s v1.12). This frees the
> kubernetes-plugin from caring for the Pods after build completion.
>
> Has anyone experience with kubernetes Jobs? Am I missing something obvious?
>
> @Carlos Sanchez: If not, I would try to implement this in your
> kubernetes-plugin. Would you be interested to get this back into your
> mainline? Then I would fork the github repo and start directly off master.
>
> Regards,
> Daniel
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/1fe306b4-f8f6-48b1-a98a-087b119f880f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1fe306b4-f8f6-48b1-a98a-087b119f880f%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6N4Z4fwADnCL7khj3Ey%3D9dg1%2BA--VN85FNi9bBKmiRHiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin and Configuration as Code Plugin

[Carlos Sanchez]

can you post the specific error

On Wed, Sep 12, 2018 at 4:11 PM Emir Özbir 
wrote:

> Sorry about that
> I want write " your image has some spesific configuration"  for
> configuration aa code plugin
>
> 12 Eyl 2018 Çar 12:03 tarihinde Carlos Sanchez  şunu
> yazdı:
>
>> can you post the specific error
>>
>> > Maybe csanchez/jenkins-kubernetes-configuration-as-code has a some
>> spesific error .
>>
>> I thought you said that image worked and the one you provided didn't
>>
>>
>> On Wed, Sep 12, 2018 at 10:18 AM Emir Özbir 
>> wrote:
>>
>>> I've a big trouble with KUBERNETES and Configuration as code plugin .
>>>
>>> When I try demo at
>>> https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/kubernetes
>>> .
>>>
>>> I 've no problem master can create slaves and run the jobs very well but
>>> when I change image at name at demo yamls kubernetes image and also
>>> configuration yaml , jenkins raise an bad error .
>>>
>>> The error is about Kubernetes Launcher error and exception is
>>> NoTaskAccepting .
>>>
>>>
>>> Maybe csanchez/jenkins-kubernetes-configuration-as-code has a some
>>> spesific error .
>>>
>>> Help me for this problem thank you .
>>>
>>> Best Regards
>>> Emir
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/3f09fa89-aa37-4173-bff0-2387ad06e699%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/3f09fa89-aa37-4173-bff0-2387ad06e699%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PMtVFTGmeJJri14yuRkSfLx6aah-oGjManFq1Mx3JNVg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PMtVFTGmeJJri14yuRkSfLx6aah-oGjManFq1Mx3JNVg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAEHNYcy7uZMcPfF2W9ZTrJfwYe6F8%2B4--pUM_pAvfqyG0J9wVw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAEHNYcy7uZMcPfF2W9ZTrJfwYe6F8%2B4--pUM_pAvfqyG0J9wVw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6MVbeVs-4%2BU6SsZ5bBYmpbV%2B%3DfKLnuP%3Ds%2BdbFC%2B2MT%2Bkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin and Configuration as Code Plugin

[Carlos Sanchez]

can you post the specific error

> Maybe csanchez/jenkins-kubernetes-configuration-as-code has a some
spesific error .

I thought you said that image worked and the one you provided didn't


On Wed, Sep 12, 2018 at 10:18 AM Emir Özbir 
wrote:

> I've a big trouble with KUBERNETES and Configuration as code plugin .
>
> When I try demo at
> https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/kubernetes
> .
>
> I 've no problem master can create slaves and run the jobs very well but
> when I change image at name at demo yamls kubernetes image and also
> configuration yaml , jenkins raise an bad error .
>
> The error is about Kubernetes Launcher error and exception is
> NoTaskAccepting .
>
>
> Maybe csanchez/jenkins-kubernetes-configuration-as-code has a some
> spesific error .
>
> Help me for this problem thank you .
>
> Best Regards
> Emir
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3f09fa89-aa37-4173-bff0-2387ad06e699%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PMtVFTGmeJJri14yuRkSfLx6aah-oGjManFq1Mx3JNVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: default container in Kubernetes plugin

[Carlos Sanchez]

You can submit a PR. Opening a ticket won't help much as I won't have time
to implement it

On Tue, Aug 21, 2018, 12:59 arch  wrote:

> ok, do I need create a ticket in
> https://issues.jenkins-ci.org/secure/Dashboard.jspa first?
>
> On Tue, Aug 21, 2018 at 6:57 PM Carlos Sanchez  wrote:
>
>> sounds good to me
>>
>> On Tue, Aug 21, 2018 at 12:38 PM arch  wrote:
>>
>>> Yes, I get your point. So I suggest offer a UI option, and let end users
>>> make choice.
>>>
>>> On Tue, Aug 21, 2018 at 6:34 PM Carlos Sanchez 
>>> wrote:
>>>
>>>> the problem is how to know when you want a container be a default, you
>>>> would need to pass it as an option in the pod template definition
>>>>
>>>> On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:
>>>>
>>>>> When I configure a pod template with java container. Then run a shell
>>>>> script in pipeline, it will cause an error that can't find command java. 
>>>>> So
>>>>> I must specify the container as java first.
>>>>> I suggest that the java container should be the default container
>>>>> instead of jnlp. Any feedback is thankful, welcome to discuss.
>>>>>
>>>>> --
>>>>> 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.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NncdK-%3DNUXQmbNb4CJ6UVu%2BquBb%2B20XoFLBTUiACAbJQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NncdK-%3DNUXQmbNb4CJ6UVu%2BquBb%2B20XoFLBTUiACAbJQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTG%2BtupG5mWpJ%2Bme%2BNECx0s%3DO%2BKaj9Se-5v2dxipru-Y6Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTG%2BtupG5mWpJ%2Bme%2BNECx0s%3DO%2BKaj9Se-5v2dxipru-Y6Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6P3N2r7js3WzCiLB1TFh%2Bx0rwAhK8-nRc-0WbtE5CRPaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: default container in Kubernetes plugin

[Carlos Sanchez]

sounds good to me

On Tue, Aug 21, 2018 at 12:38 PM arch  wrote:

> Yes, I get your point. So I suggest offer a UI option, and let end users
> make choice.
>
> On Tue, Aug 21, 2018 at 6:34 PM Carlos Sanchez  wrote:
>
>> the problem is how to know when you want a container be a default, you
>> would need to pass it as an option in the pod template definition
>>
>> On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:
>>
>>> When I configure a pod template with java container. Then run a shell
>>> script in pipeline, it will cause an error that can't find command java. So
>>> I must specify the container as java first.
>>> I suggest that the java container should be the default container
>>> instead of jnlp. Any feedback is thankful, welcome to discuss.
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NncdK-%3DNUXQmbNb4CJ6UVu%2BquBb%2B20XoFLBTUiACAbJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: default container in Kubernetes plugin

[Carlos Sanchez]

the problem is how to know when you want a container be a default, you
would need to pass it as an option in the pod template definition

On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:

> When I configure a pod template with java container. Then run a shell
> script in pipeline, it will cause an error that can't find command java. So
> I must specify the container as java first.
> I suggest that the java container should be the default container instead
> of jnlp. Any feedback is thankful, welcome to discuss.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bill of Materials

[Carlos Sanchez]

Thanks!

On Tue, Aug 14, 2018, 17:38 R. Tyler Croy  wrote:

> (replies inline)
>
> On Tue, 07 Aug 2018, Oleg Nenashev wrote:
>
> > Hi Tyler,
> >
> > Thanks for the feedback!
> >
> >
> > > I believe the only think which needs to be resolved which is likely
> just an
> > > obsolete part of the example YAML.  The root `status` key in the YAML
> for a
> > > "realized" BOM I don't believe we've ever actually used and is worth
> > > removing.
> >
> >
> > Actually I use it in some cases in order to implement custom packaging
> > Pipelines after customWARPackager()
> > <
> https://github.com/jenkins-infra/pipeline-library/blob/master/vars/customWARPackager.groovy
> >.
> >
> >
> >- BOM's specification lists explicit dependencies
> >- BOM's specification does not require all dependencies to be explicit
> >   - Some dependencies may have "dir" references
> >   - Some dependencies may be transitive. JEP-309 permits that though
> >   does not recommend for production use (dependency resolution
> >   <
> https://github.com/jenkinsci/jep/tree/master/jep/309#dependency-resolution
> >
> >   in the spec)
> >   - "status" key returns the full list of resolved dependencies
> >   - In addition to transitive deps, CWP uses "status" to squash the
> >   "environment" definitions into a single list in order to show what
> was
> >   actually packaged into the WAR file
> >
> > I would rather prefer the "status" section to stay in the specification.
> It
> > is helpful for CWP at least (though it may be possible to just generate a
> > new output BOM). If we do that, it would be nice to get feedback from
> Raul
> > who is also experimenting with processing of BOMs.
> >
> > In order to address your comment, we could explicitly say that the
> "status"
> > section is optional so that you do not need to implement it in Evergreen
> if
> > not needed. WDYT?
>
>
>
> I mentioned in a video call with Oleg this morning that I've gone ahead and
> implemented the `status` section for the  Bill of Materials being used in
> the
> jenkins-infra/evergreen repository.
>
>
> Overall I'm quite happy with this work by Oleg and Carlos, and I will be
> submitting a PR (with my BDFL-Delegate hat on) to mark JEP-309 as
> 'Accepted'
> later today.
>
>
> Thanks for the  hard work everybody!
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/20180814153826.GH17800%40grape.lasagna.io
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PqFiccFSz-tT91O4W0c45OC_2QGdq-_x9E8X9jSsomwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] Jenkins Remoting over Message Bus/Queue Introduction

[Carlos Sanchez]

Very cool, looking forward to it !

On Fri, May 18, 2018 at 7:51 AM Pham Vu Tuan  wrote:

> Hi all,
>
> My name is Vu Tuan, and I am participating in Jenkins Google Summer of
> Code this year as a student. My project is Jenkins Remoting over Message
> Bus/Queue
> .
> Some background about this project:
>
>- Current versions of Jenkins Remoting are based on the TCP protocol.
>If it fails, the agent connection and the build fails as well. There are
>also issues with traffic prioritization and multi-agent communications,
>which impact Jenkins stability and scalability.
>- This project aims an update of Remoting and Jenkins in order to add
>support of a popular message queue/bus technology (RabbitMQ or Kafka) as a
>fault-tolerant communication layer in Jenkins.
>
>
> Currently we are in the first phase of the project and I am going to
> implement a PoC in this first phase. The messaging technology used is
> Apache Kafka, and the deliverable for the first phase will be in Docker
> compose with multiple services and components involved.
> If you are interested, we have a gitter
>  chat for this project. The weekly
> meeting schedule is:
>
>-
>
>Every Tuesday, 02:00-03:00 PM UTC
>-
>
>Every Friday, 02:00-03:00 PM UTC
>
> I am looking forward to contributing to Jenkins community this summer.
>
> Best regards,
> Pham Vu Tuan
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/22237593-3392-4a88-9267-634c8827b50b%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Ng%2BQRdAuZBb3BssT8qLNU5TBFaCnQOJgk9B%3DxmQ4zp5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bill of Materials

[Carlos Sanchez]

On Fri, May 11, 2018 at 11:44 AM Oleg Nenashev 
wrote:

> Hi all,
>
> Just to provide an update on this topic, I have added support of Bill of
> Materials (in the current draft version) to Custom WAR Packager
>  and used it in several
> automation flows. E.g. see Integration Testing for Artifact Manager S3
> . I can
> also rework Remoting (PR) 
> and Stapler (PR) flows to
> use BOM there if it is needed for a reference implementation.
>
> Do I gravely need BOM in these pull requests? The answer is "No" as Jesse
> pointed out. Custom WAR packager uses its own YAML format
> 
> which can be integrated into essentials.yml format created by Raul
> Arabaolaza  for integration tests.
> This format is generally more flexible for packaging WARs for testing
> purposes (build settings, relative FS paths, support of embedding System
> properties and Groovy scripts, etc.). In this PR
>  and JEP
> comments I have pointed out several weaknesses of the current BOM proposal:
>
>- The provided justification for BOM is true, but actually it is
>already achieved by Custom WAR Packager.
>- BOM does not make much difference there as described above
>   - "We want to unify the description format across projects within
>   Jenkins (e.g. Jenkins Essentials, Jenkins X, Docker Packaging, etc.)." 
> is
>   the real thing we should focus on IMHO, but it needs to be expanded (see
>   proposals below)
>   - BOM format is not specified. The JEP proposal just provides an
>example without specifying fields. It refers the K8s notation, but that's
>it. There is no link to K8s specification and the version, and this
>specification may drift over time. It leads to all my further comments here
>- "Metadata/labels" are not specified. What is a "must", what is
>"optional"?
>- E.g. what is field 'name' and how should it be used?
>   - Purpose of "Metadata/annotations" section is not clear.
>- There is neither examples nor documentation
>   - I would expect to be able to put any custom data there. E.g. for
>   Custom WAR packager I would expect to put build and packaging settings
>   there. OTOH for Jenkins Essentials I would expect this section to have 
> some
>   deployment rules and so
>   - We had a private discussion with Carlos, and his explanation was
>   that "annotations" in K8s notation is just a key-value mapping without
>   object support. It does not allow passing complex configurations via 
> them
>   and hence does not allow using BOM as a sole input for test automation
>   flows (like ATH which is used for justification)
>   - "Core" section needs specification
>   - I'd guess it defines version of WAR file, but it's not clear from
>   documentation. Note that version of WAR and version of the bundled 
> Jenkins
>   Core may differ (timestamped releases, custom WAR builds, etc.)
>   - "Core" does not define "artifactId" or "groupId". It means that
>   only standard Jenkins WAR "org.jenkins-ci.main:jenkins-war" may be used.
>   What if I want to define BOM for a custom product based on Jenkins? It 
> is a
>   real use-case for me
>   - Vague "components" section. It is not clear what can be defined
>there and how it should be handled.
>   - Is it only JARs? What about Jenkins Modules, Resources, System
>   Groovy Scripts, etc.
>   - There is no "type" field or whatever which would allow to
>   distinguish it
>   - Plugins and Components support only "version" and "ref" fields
>   - In test automation flows we need to test unreleased components in
>   repositories, and it would be really useful to just reference 
> components by
>   path to sources and by path to HPI/JAR like it's done in custom WAR 
> packager
>- It is not clear how "environment" should be used.
>- Can we define multiple environments? Or just a single one?
>   - Can environments override plugins/components? Or do they just
>   append new ones?
>- "status" section requires all components/plugins to have
>artifactId/groupId/versions
>   - What if I add a "Groovy init gook" script from a repository as a
>   component? This component has no real version since it's not released
>   separately. Am I expected to mock them somehow (e.g. commitId)?
>   - Does BOM expect all listed components to be available in Maven
>   repo?
>
> IMHO BOM specification should be created and documented properly, maybe
> using one of standard YAML specification languages.
>
>
> Even with the 

Bill of Materials

[Carlos Sanchez]

Hi there,

I have filed a new JEP to address the concept of Bill of Materials (BoM).

*https://github.com/jenkinsci/jep/pull/92
*

The BoM idea came up after different conversations with Tyler/KK/Oleg and
several more people - thanks for the feedback! - talking about how can we
define a Jenkins package ("classic" jenkins, essentials, custom) to ensure
that latest master of core and plugins can be easily used and tested, as
well as the too typical use case of PRs in progress across multiple modules.

The main goal is to increase velocity by providing developers automatic
artifacts and the result of tests against those artifacts before these
combinations of PRs are merged. In order to create some safety nets that
encourage contributions and facilitate reviews.

Please share your feedback

Thanks!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PNnYTpF-0mnr0_pee9yw0tYaX%3D%2B6akgBNp%3DXnMgToOrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins External Artifact Storage core changes in LTS

[Carlos Sanchez]

On Mon, Apr 16, 2018 at 9:32 AM, Oliver Gondža  wrote:

> Thanks for the details, guys. I have rechecked all new API is annotated
> with Beta. I am wondering, what plugins are going to consume this? I am
> trying to understand what userbase will be exposed to the change, what use
> cases can be affected.
>

To be clear, this would be for the next LTS picked in May, not for the
current in progress one.

Existing artifact manager usage is unaffected, everything continues to work
as before storing things on disk.
Only when the new plugin implementing the artifact manager for s3 is
enabled artifacts would go to S3

https://github.com/jenkinsci/jep/blob/master/jep/202/README.adoc#prototype-
implementation

The new one is artifact-manager-s3-plugin


Related PRs

   -

   JENKINS-26810  File
   attribute/symlink support in VirtualFile - fixed as a side effect
   -

   JENKINS-49635  Permit
   VirtualFile to serve external file contents
   -

   Jenkins core PR-3302 
   -

   WAR packaging implementation for the reference implementation
   

Downstream improvements to use the new APIs

   -

   workflow-api-plugin PR-67
   
   -

   workflow-basic-steps-plugin PR-60
   
   -

   copyartifact-plugin PR-100
   
   -

   compress-artifacts-plugin PR-1
   




>
> Having said that, I see this backportable into .3 provided it will be
> merged by the end of the backporting window. Also, It would be great if you
> can either provide ATH tests for the new plugin functionality for RC
> testing window or retest and report during that window.


> Thanks!
> --
> oliver
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/9760335c-57cd-0d30-cc90-0053107cfbcb%40gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6MTY1qEH4uQhdr0%2BoA7rsHKU4AxFhaz3MjtQ%3DOg%2BbLirw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins External Artifact Storage core changes in LTS

[Carlos Sanchez]

On Fri, Apr 13, 2018, 22:08 R. Tyler Croy <ty...@monkeypox.org> wrote:

> (replies inline)
>
> On Fri, 13 Apr 2018, Oliver Gond??a wrote:
>
> > On 2018-04-13 18:23, Carlos Sanchez wrote:
> > > Hi Oliver,
> > >
> > > There are some changes for core that would be really helpful to have in
> > > hands of people for testing sooner than later
> > >
> > > https://github.com/jenkinsci/jenkins/pull/3302
> > >
> > > All new methods are marked with the new @Beta annotation so it should
> be
> > > clear that it's not final.
> > >
> > > We expect this to be in the next weekly or so,but I would really like
> to
> > > ensure we can pull this into the next LTS if at all possible,what can I
> > > do to help prepare these changes for the LTS,even if we tried to
> > > backport it?
> >
> > Hi, Let's make the discussion public.
> >
> > My personal take is the LTS and Beta.class are quite orthogonal in
> > principle. When it comes to the actual change, it feels far from trivial
> for
> > such an exception IMO. What is the motivation here? Backporting this will
> > get it in LTS in 4 weeks, otherwise it will get in in 8 weeks.
> >
> > Thoughts? I would really like to avoid backporting something before it
> has
> > its final shape (IOW, merged to master).
>
>
> Hey Oliver, I was chatting with Carlos about this earlier and encouraged
> him to
> reach out to you to better understand your thoughts for considering code
> coming
> into the LTS.
>
> From my understanding of what Carlos is asking about, is not pulling
> anything
> into an LTS which isn't already in a Weekly release. Rather, I think
> Carlos is
> apprehensive about the timing between Weekly releases and LTS, and is
> worried
> about missing the last Weekly before our typical 2-weeks-before LTS
> cutoff."
>
> I think Carlos's team has worked quite hard to get the underlying code to
> enable external artifacts ready, and considers one indication of "success"
> to
> have that code delivered in our next LTS cycle, since LTSes are consumed
> by the
> vast majority of Jenkins users who would benefit from this functionality.
>


Tyler has summarized it correctly, I expect this to be in master soon but
just want to make sure we don't miss the LTS.

Getting useful feedback and having final implementations ready in the
future for this type of change relies on putting this in the hands of as
many people as possible.

That's why the API changes use @beta annotations (and I believe we would be
the first ones using it), to get new functionality in the hands of users
asap, improve the velocity of new feature delivery while ensuring that
stability is not affected.

Cheers




>
> I *hope* I've captured the situation clearly.
>
>
> The questions Carlos has about LTS timing I think are all moot assuming
> that
> the aforementioned pull request gets reviewed and merged in a timely
> manner for
> next week's release (from my understanding).
>
>
>
> Cheers
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NF_gvKf955%3DAcPfunkbO%2BfaqwbuYMM0EMgO_QVumKUSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: External Artifact Storage

[Carlos Sanchez]

PR submitted at https://github.com/jenkinsci/jep/pull/83

On Fri, Apr 13, 2018 at 5:24 PM, Oleg Nenashev 
wrote:

> Looks good to me **as a DRAFT**.
> Please propose a pull request so that JEP editors can review it.
>
> We also need somebody to be selected as BDFL Delegate if KK is not
> available to review it.
>
> BR, Oleg
>
>
> On Friday, April 13, 2018 at 4:25:38 AM UTC+2, Jesse Glick wrote:
>>
>> +1
>>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/0851cc7d-d3cc-4da9-8a76-b841817e38da%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6P6vQxzVXmLLQnff7CFeOTYbC6aF7OmM-KVBM%2BXwGPbjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

External Artifact Storage

[Carlos Sanchez]

Hi there,

With the goal to make Jenkins more "cloud-friendly" or "cloud-native" I
have created a JEP draft to enable the storage of artifacts outside the
Jenkins home, ready for review

https://github.com/carlossg/jep/tree/jep-submission/jep/

TL;DR

Adding an ArtifactManager implementation (with required core changes) that
transparently stores artifacts in a external blob store / artifact
repository. First implementation using AWS S3

Please share your feedback

Thanks!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Pqc_1CCzqJcLsqmA62uEwsn4pvkFpYR9K0Hp6-ygPc_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Change Jenkins default logging format

[Carlos Sanchez]

I'm +1 to change the format. 2 lines is really annoying

On Wed, Apr 4, 2018 at 7:24 PM, R. Tyler Croy  wrote:

> (replies inline)
>
> On Wed, 04 Apr 2018, Oleg Nenashev wrote:
>
> > Hi Baptiste,
> >
> > Anyone can easily change the logging format in Jenkins by passing custom
> > J.U.L properties file.
> > So it should not be a problem to change logging format even if you do not
> > add a custom logging appender for ELK.
> >
> > Changing a default logging format may cause regressions in existing
> > monitoring systems. I would rather be conservative and keep the default
> > logging format in Jenkins unless there is a strong justification to do
> > that. New subprojects like Jenkins Essentials and Jenkins X could easily
> > change the default format, because they have no compatibility commitment
> so
> > far.
>
>
> Thanks for sharing your thoughts Oleg, it makes me wonder: how could we
> quantify the positive/negative impact of this (arguably) "bad default."
>
> I'm reminded of some of the pre-Jenkins 2 discussions about security
> defaults
> for example. I spent some time trying to discover Jenkins-log-parsing
> projects,
> tools, and their communities to which we could reach out. Unfortunately I
> wasn't able to find anything big past a couple of blog posts :-/
>
> From my personal experience as an Operator, compact and easily parseable
> (sed/awk/perl) one-line logs are HUGELY valuable and worth any temporary
> heartburn some people may experience with their existing hacks.
>
>
>
> Cheers
>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/20180404172432.wlr4c5f35tuvnijj%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NsdOsMRtD%3DacAATvOiY_Wo15gxu6Fwh5iRCs3ogqMmfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JEP: Modification of "Accepted" JEPs

[Carlos Sanchez]

I agree with Ewelina that *"all 'significant changes' to a JEP should be
completed before it is Accepted"*  looks like a requirement that may hinder
innovation and experimentation on areas that are not clear from the start.
I'd rather see a review process that can return the JEP to a draft state
for a v2 where people can discuss the new changes


On Fri, Mar 23, 2018 at 7:53 AM, Ewelina Wilkosz 
wrote:

> I'm perfectly ok with starting a discussion about proposed change
>
> And in general I do not disagree with your proposal but I want to share my
> doubts... when we started working on Jenkins Configuration as Code we had
> an idea and then the idea has changed and I'm glad we put it all in one
> document. Now when I see a requirement *"all 'significant changes' to a
> JEP should be completed before it is Accepted"* it makes me worry that if
> I end up working on next JEP, for another project, I will be very careful
> and it will take ages to put it into "Accepted" (maybe it's not a problem).
> And then, like with JCasC, we learn while we implement it, we discover
> issues and things that we can't do the way we want to do. Do we have to
> discover all of that before "Accepting" JEP? That is the first thought that
> came into my mind.
>
> Maybe it is exactly what you want and I can fully understand that. It just
> seems to me now that it is much more formal that I expected at the
> beginning.
> Maybe it's because it's a new process, or I just missed some information,
> but then we should probably make sure that the information is there. We had
> a short discussion about that on Gitter lately, about purpose of JEP and
> which kind of things require JEP. You know that, a lot of people know, but
> many don't. Maybe it wouldn't be the worst idea to organise a Jenkins
> Online Meetup around JEP concept?
>
>
> BR
> Ewelina
>
> On Friday, March 23, 2018 at 12:47:52 AM UTC+1, Liam Newman wrote:
>>
>> We recently had a pull request with a number of significant changes filed
>> against JEP-201 which has already been "Accepted" (see the JEP workflow
>> outlined in JEP-1 
>> ).
>>
>> https://github.com/jenkinsci/jep/pull/59
>>
>> This poses a problem because the JEP workflow doesn't contain guidance
>> for making/tracking significant changes to JEPs.  The intent of the process
>> is for all major changes to land while the JEP is a "Draft". A JEP being
>> "Accepted" means that a general consensus was reached regarding the design
>> and scope of the component/area described by the JEP.  Once a JEP is marked
>> "Final", the workflow specifically states that changes should be made by
>> filing a new JEP and marking the old one as  "Superseded" when the new JEP
>> is complete.
>>
>> I would like to add the following clarifications to JEP-1:
>>
>>1.  State specifically that all "significant changes" to a JEP should
>>be completed before it is Accepted. This is pointed to in a number of
>>places but may not be mentioned explicitly.
>>2. Define a "significant change" is any change that would modify the
>>intent, scope, API, or overall behavior of the component.  I will provide
>>some examples.
>>3. If "significant changes" are proposed to an "Accepted" JEP, it is
>>be the responsibility of the Sponsor to communicate those changes on the
>>mailing list and make sure that people have sufficient opportunity to
>>review and comment before merging those changes.  A link to the thread
>>should be included in the PR for the change and in the References section.
>>4. If there are strong objections to the proposed change, the
>>Reviewer of the JEP may choose to return the JEP to a "Draft" state for
>>continued discussion and re-review.
>>
>> (Items 1 and 2 are both clarifications. Item 3 is a reiteration of the
>> existing responsibilities of the JEP Sponsor in light of 1 and 2.  4 is a
>> reiteration of the existing of responsibilities and powers of the JEP
>> Review in light of 1 and 2.)
>>
>> In the case of the above PR. it means that Ewelina would need to start a
>> thread on the mailing list to discuss this change and give people time to
>> review before we merge that change.
>>
>> What do people think of this?  An feedback or suggestions?
>>
>> Thanks,
>> Liam Newman
>> JEP-1 Sponsor
>>
>> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/6b84a0b5-a23b-44cf-80b3-faac982448ac%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this 

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Carlos Sanchez]

I think the materialization of SIGs would be a great addition to the
community, thanks Tyler for the write up

I am working on draft JEPs to be proposed regarding "cloud native":
external storage, external logging,... you'll be reading more from me in
the following weeks :)


On Thu, Mar 22, 2018, 22:04 R. Tyler Croy  wrote:

>
> I have been looking at some of the great things the Kubernetes community
> has
> been doing for ideas we can borrow, and one idea which really sticks out
> is:
> Special Interest Groups (SIGs)
>  master/governance.md#sigs>
>
> A full list of the Kubernetes community SIGs can be found here:
> 
>
> I think we already have some groups, which are almost informal SIGs, such
> as
> Security, GSoC, Infra, etc. The aspects of SIGs which I really would like
> to
> formalize, and support from a community infra standpoint are:
>
> * Clear problem domain/focus area.
> * Regularly scheduled and published meetings. I can easily imagine
> re-using
>   #jenkins-meeting or our public YouTube channel for regularly
> scheduling
>   and hosting weekly meetings for these various groups. I run a weekly
>   infra team sync on jenkins.io/hangout for example, but that's not
>   recorded anywhere :(
> * "Chairs" (i.e. team leads)
> * Dedicated discussion channel/group (i.e. mailing list)
>
>
> Some SIGs which I would love to see for starters, would be:
>
>  * Security, lead by Daniel
>  * GSoC, lead by Oleg
>  * Infra, lead by Olivier and myself
>  * Cloud Native (Kubernetes, Jenkins X, CLOUD, etc), lead by Carlos
>  * Essentials, lead by myself
>  * LTS, lead by Oliver
>  * Automation/Configuration (config as code, puppet, chef, etc), lead by
> Ewelina
>
>
> From my part on the infrastructure side, I'm more than willing to do the
> necessary work to support SIGs, as I really feel like they will help bring
> more
> folks to the table for focused contribution to the Jenkins project.
>
>
> I'm curious how others feel about a SIG structure and whether you all agree
> that it will help channel/focus discussions and contributions?
>
>
>
> If there's strong interest, I'm happy to take point on writing a Process
> JEP.
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/20180322210421.4ikcudf7m65yilvo%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OE--pazM4C%2BFt6F066PfmhP5L7s2ZQX3AB6NW_uQo2rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: alpha version of Jenkins Configuration as Code plugin available

[Carlos Sanchez]

awesome!

does 0.1 need the "alpha" label? :)

On Mon, Feb 26, 2018 at 5:00 PM, Ewelina Wilkosz 
wrote:

> Last Friday we've released 0.1-alpha of Jenkins Configuration as Code
>  plugin. Use
> carefully, number of key features still missing but we're getting there!
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/24e6979e-aff9-45cd-885f-8520ec2fe3eb%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OhpBzpGi6T%3DxRWbTs%3DrYqf1eK03H5T65iVYQSzn6mTVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Evergreen packaging for Jenkins Essentials

[Carlos Sanchez]

yay! +1

I agree with previous comments that it is not ideal to run multiple
processes and that in a kubernetes world this would possibly be a Pod with
two containers, but I think it's important to get something out and
iteratively improve.
A decent user experience today means just one container and we can always
had a Pod definition for Kubernetes users if we find that useful in the
future.

Regarding different environment autodetection it would be nice, but having
a way to manually select it (system property, env var,...) would be good
enough for now



On Wed, Feb 7, 2018 at 10:28 PM, R. Tyler Croy  wrote:

> In the same vein as my previous email, I've written up a design document
> which
> outlines the current approach for packaging I intend to use for Jenkins
> Essentials:
>
> https://github.com/jenkinsci/jep/tree/master/jep/301
>
> I think it should be fairly straight-forward and understandable why I'm
> taking
> the approach described, but if there any ambiguity do let me know.
>
> Please take a look at the document and let me know what you think on this
> thread :)
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OZTJSNnA3JZ1Er4XvpiEW55LpfR73Zz5D_x%3D9OSG5i5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Asking for commiter access to amazon-ecs-plugin

[Carlos Sanchez]

Created https://issues.jenkins-ci.org/browse/INFRA-1501 to follow

On Thursday, January 4, 2018 at 6:51:18 PM UTC+1, Jordi Miguel wrote:
>
> Hi all,
>
> It's been more than one month since last message on this thread and we 
> still don't see any progress to unblock development. I'm sure Jan made a 
> good job while he was leading the plugin's development and we thank him for 
> it. Unfortunately he doesn't seem to be active anymore so, can we give 
> commit permissions to someone who's active? On previous messages looks like 
> Douglas Manley was happy to take over the role and I suspect he has not 
> changed his mind.
> I don't care much who ends up being the new maintainer but we're 
> approaching the year mark since the last commit that found its way to 
> master's branch and there are plenty of PR's waiting for a merge that 
> haven't succeed because we don't have anyone with write permissions in the 
> active community.
>
> I hope we can find a solution to this issue soon. If there is anything I 
> can do to help resolve problems please don't hesitate to ask.
>
>
> Thanks,
> Jordi
>
> El miércoles, 29 de noviembre de 2017, 21:39:40 (UTC+1), Yaramada Surya 
> tej escribió:
>>
>> Hi Mathus,
>>   It would be great if any one can change the maintainer 
>> of this plugin to Douglas as he is willing to took it so that we can 
>> utilize this plugin , many of us are waiting to get this pull request 
>> merged.
>>
>>
>> Thanks
>> Surya
>>
>> On Thursday, 7 September 2017 17:33:57 UTC-4, Baptiste Mathus wrote:
>>>
>>> Hello,
>>> Seems like Jan is not active either these days or anymore at all.
>>>
>>> So either you can see if you want to adopt this plugin (in that case 
>>> please follow the process described on the wiki), or this is likely to stay 
>>> this way until someone does I suspect.
>>>
>>> Baptiste
>>>
>>> Le 7 sept. 2017 17:22, "Surya yaramada`"  a écrit :
>>>
 Hi,
  I am sorry for interrupting again but can I please know if there 
 is a chance to merge the pull requests for AMAZON-ECS plugin.


 Thanks 
 Surya

 On Thursday, August 24, 2017 at 4:12:47 PM UTC-4, Daniel Beck wrote:
>
>
> > On 24. Aug 2017, at 22:09, Surya yaramada`  
> wrote: 
> > 
> >  Can I get any updates on this? 
> > 
>
> There's no need for multiple emails per day. Give him a week or so. 
> Jan may well be on vacation. 
>
> -- 
 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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/4f569b34-cfb3-427f-adc3-40406f9c6b3e%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f20148e3-4ce6-49b9-9acb-c432a50298d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Renaming credentials classes

[Carlos Sanchez]

It's all good now, had to upgrade the credentials plugin to a version that
actually used Jenkins.XSTREAM2

On Thu, Jan 4, 2018 at 1:00 PM, Robert Sandell <rsand...@cloudbees.com>
wrote:

> System credentials seems to be using Jenkins.XSTREAM2 at least
> https://github.com/jenkinsci/credentials-plugin/blob/
> master/src/main/java/com/cloudbees/plugins/credentials/
> SystemCredentialsProvider.java#L126
>
> User credentials is "just" stored in a user's properties
> https://github.com/jenkinsci/credentials-plugin/blob/
> master/src/main/java/com/cloudbees/plugins/credentials/
> UserCredentialsProvider.java#L463
>
> The default store implementation delegates to the store's context
> https://github.com/jenkinsci/credentials-plugin/blob/
> master/src/main/java/com/cloudbees/plugins/credentials/
> CredentialsStore.java#L573
>
> So you seem to be using the correct XStream instances.
>
> /B
>
> 2017-12-29 13:01 GMT+01:00 Carlos Sanchez <car...@apache.org>:
>
>> Hi
>>
>> Trying to get this PR to work on upgrades
>> https://github.com/jenkinsci/kubernetes-plugin/pull/268/file
>> s#diff-14316beac1f1489a56a52e21cf8e0ee6R506
>>
>> but none of the XSTREAM2.addCompatibilityAlias options listed in
>> https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining
>> +backward+compatibility seem to work, the credentials are never
>> deserialized
>>
>> Any suggestions?
>>
>> --
>> 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.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%2B3Zd6Bstk3
>> qtbvcBAQoq-7OOA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%2B3Zd6Bstk3qtbvcBAQoq-7OOA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CALzHZS3PP_v7Q9sZC1JPZOR%2B2N%
> 3D-jet293vD6ACb_rh0ob6ZFA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3PP_v7Q9sZC1JPZOR%2B2N%3D-jet293vD6ACb_rh0ob6ZFA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OXppQWfNEN8ABAZRUUhb85KX08EVeJM2b%3DBiwf6H_b3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Renaming credentials classes

[Carlos Sanchez]

Hi

Trying to get this PR to work on upgrades
https://github.com/jenkinsci/kubernetes-plugin/pull/268/files#diff-14316beac1f1489a56a52e21cf8e0ee6R506


but none of the XSTREAM2.addCompatibilityAlias options listed in
https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility
seem to work, the credentials are never deserialized

Any suggestions?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%2B3Zd6Bstk3qtbvcBAQoq-7OOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: mvn hpi:run fails with NullPointerException

[Carlos Sanchez]

Try running mvn package hpi:run
There is a filled issue about that if you have run clean before hpi:run

On Tue, Oct 31, 2017, 21:18 Jean-Karlo Accetta 
wrote:

> Hi all,
>
> I am new to developing plugins for Jenkins, and I was reading several of
> the related pages on getting started.  The problem is that whenever I try
> to run any build step or goal, it fails.  I tried first with the hpi:run
> command they say to use for debugging, but any goal will result in the
> following error:
>
> [*ERROR*] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> *(display-info)* on project jenkins-plugins: *Execution display-info of
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> failed.*: NullPointerException -> *[Help 1]*
>
> I'm not sure what is going on, but all my other maven projects work fine.
> I'm not sure if it's an issue with maven's settings.xml or if it's an issue
> with the plugin's pom or something.
>
> Any help would be appreciated, and please let me know if more information
> (the full log or the pom or something) would be helpful.
>
> Thanks,
>- JK
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/f03a7004-689f-4d97-a260-33caa81a0875%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6N02uR%2BmJ8O2Em4t-GBBZMK_MzHUPMV3GL%2B0YuYgqf8xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to define labels and executor thread count for docker-jnlp-slave?

[Carlos Sanchez]

that's all defined in jenkins side, not in the agent
you can use the swarm plugin for auto connections

On Mon, Aug 21, 2017 at 3:57 PM, Kirill  wrote:

> Hi folks,
>
> I'd like to use docker-jnlp-slave in my docker-compose to spin up slaves
> for Jenkins master.
> However, I didn't find a way to define the labels for the agent - seems
> that there's no parameter for that. The same for executor thread count.
> Furthermore, the Main class of JNLP agent (https://github.com/jenkinsci/
> remoting/blob/master/src/main/java/hudson/remoting/jnlp/Main.java)
> doesn't seem to support these parameters as well. However, in agent's
> details in UI you can define these things.
>
> So is there still a way to define those on container start? Or maybe I
> should just use an empty busybox-style container calling create-node CLI
> command (e.g, https://stackoverflow.com/questions/42683324/create-
> jenkins-jlnp-slave-programmatically/42703928#42703928) to create a JNLP
> agent?
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/b4602caa-73e3-4fc5-b311-b0a9a0f91b26%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6ODgk2gop7bsyV4zCaUu90mJczZc12ftbduSZ35KbH%3DFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Customize node creation from within a pipeline definition

[Carlos Sanchez]

The kubernetes plugin does that, so you can check for inspiration
https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#pipeline-support

It would be nice to have a common syntax across container provisioners

On Tue, Jul 25, 2017, 14:55 Jesse Glick  wrote:

> The argument to `node` is a label expression, and the `Cloud` SPI
> allows interpretation of labels, so you could probably write something
> like
>
> node('nomad && nomaddocker:internal/jenkins-worker:v12 &&
> nomadmemlimit:4Gb') {…}
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr166Uu4%2BjQn%2By5_Yy8%3DzuvBor_ADLqidr0K_0%2BzyWG7Tg%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6MuxFMor-DnOtaBS%3DBE60-88tZ%3D6EBedsHfBbTjpMyr5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: "SEVERE: Error while pumping stream. java.io.IOException: Pipe broken" errors when I building a job including shell script in Kubernetes with the Kubernetes plugin

[Carlos Sanchez]

Yes, there are some issues with the container() step that I'm trying to fix
as part of https://issues.jenkins-ci.org/browse/JENKINS-42048
I don't recommend using container() until the next release

On Tue, Jun 6, 2017 at 5:31 PM, 李立  wrote:

> We have Jenkins running in Kubernetes with the Kubernetes plugin, and have
> been experiencing some exceptions when building job which includes shell 
> script
> .
>
>
> The following is exceptions infomation. And every shell command causes a
> exception, for example, my job execute 10 times shell command and throw 10 
> exceptions
> infomation as follow.
>
> Jun 06, 2017 9:45:33 PM io.fabric8.kubernetes.client.utils.InputStreamPumper
> run
> SEVERE: Error while pumping stream.
> java.io.IOException: Pipe broken
> at java.io.PipedInputStream.read(PipedInputStream.java:321)
> at java.io.PipedInputStream.read(PipedInputStream.java:377)
> at java.io.InputStream.read(InputStream.java:101)
> at io.fabric8.kubernetes.client.utils.InputStreamPumper.run(
> InputStreamPumper.java:48)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
>
> We're using the following pipeline:
>
> podTemplate(label: 'test_pipeline_execute_time_1', containers:
> [containerTemplate(name: 'ubuntu', image: 'ubuntu', ttyEnabled:
> true,command: 'cat')])
> {
>   node('test_pipeline_execute_time_1'){
>  container('ubuntu') {
>   for(int i=0;i<10;i++)
> {
>  sh 'ls '
> }
> }}}
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/e12fd96e-dd85-43e6-8911-a18bb87c8074%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6P6c5kgNgFnMZyw2hT50hAPqzgU61kv5gX4jc5W0709gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: confusion of Kubernetes plugin source code

[Carlos Sanchez]

Not sure what you mean, but there is a wait to ensure the pod is started.
Although that should be changed to retries

On Thu, May 18, 2017, 16:44 李立  wrote:

>
> Hello  ! When I study the code of Kubernetes plugin and I encounter a
> difficult.
> In the method named "call" of class ProvisioningCallback of
> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud file, I see waiting
> 6s after log "Waiting for Pod to be scheduled". Why I don't find anywhere
> waiting 6s in  the whole build process.
> [image: 内嵌图片 2]
> I will be looking forward to your reply！Thanks！
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/c50d389d-7a89-4456-8f37-f84994c91368%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6MG7m_VvbWD9e5%2BOz5yGUvG%2B2TchKnQkVPRqhn5CYJKCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to set the property of "Time in minutes to retain slave when idle" in podTemplate

[Carlos Sanchez]

it doesn't make sense to retain a slave declared in pipeline, as it is
supposed to run only for the operations inside its brackets

On Fri, May 12, 2017 at 3:32 AM, 李立  wrote:

> I see the the property of "Time in minutes to retain slave when idle" in
> jenkins configure when I use Kubernetes plugin. But I want to configure
> this property in podTemplate, just as
>
> podTemplate(label: 'mypod', containers: [
> containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', 
> ttyEnabled: true, command: 'cat'),
> containerTemplate(name: 'golang', image: 'golang:1.6.3', ttyEnabled: 
> true, command: 'cat')
>   ]) {
>
> node('mypod') {
> stage('Get a Maven project') {
> git 'https://github.com/jenkinsci/kubernetes-plugin.git'
> container('maven') {
> stage('Build a Maven project') {
> sh 'mvn clean install'
> }
> }
> }
>
> stage('Get a Golang project') {
> git url: 'https://github.com/hashicorp/terraform.git'
> container('golang') {
> stage('Build a Go project') {
> sh """mkdir -p 
> /go/src/github.com/hashicorpln -s `pwd` 
> /go/src/github.com/hashicorp/terraformcd 
> /go/src/github.com/hashicorp/terraform && make core-dev"""
> }
> }
> }
>
> }
> }
>
>
> How to set the Time in minutes to retain slave when idle in mypod ?
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/f64a56a6-9e79-468c-82e9-762f40693c86%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6N0-%2B5NO_tQvUWsW8vN_vJ3TTEmL-X6X-6mLDFArqhpRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Users, Jenkins Issues banned from Google Groups?

[Carlos Sanchez]

There is an option to moderate the first post from users

On Tue, Apr 11, 2017 at 9:42 AM, Arnaud Héritier 
wrote:

> Thus if you are already deleting them manually after they are submitted it
> means that we need to activate the moderation on the list to be sure that
> they never arrive ?
>
> On Tue, Apr 11, 2017 at 12:51 AM, R. Tyler Croy 
> wrote:
>
>> (replies inline)
>>
>> On Mon, 10 Apr 2017, Arnaud H?ritier wrote:
>>
>> > The only solution is to moderate the list and avoid spams (if not too
>> late)
>> > Perhaps an admin can delete spam messages in the group ...
>>
>>
>> I do this every single morning. Over the weekend I didn't, and I guess we
>> got
>> unlukcy.
>>
>>
>> There are three other moderators who have been coasting while I do all the
>> dirty work though... :)
>>
>>
>>
>> Arnaud, if you wish to join the spam brigade, that can be arranged :)
>>
>>
>>
>>
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>  xmpp: rty...@jabber.org
>>
>>   % 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/20170410225149.bjaldrprxv5dtqc2%
>> 40blackberry.coupleofllamas.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAFNCU--_Ka%3DB8i6-eAzaAyeiJYNBd2LNX_
> asmSJ-WMq_swBarA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OdtZmSr5ANUVLK_oAwxYeTG2UZPGNYisxGm2r0YsxJAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes plugin

[Carlos Sanchez]

That's the way the cloud api works, you can try setting the system
property hudson.slaves.NodeProvisioner.initialDelay=0

On Wed, Apr 5, 2017 at 9:54 AM, 李立  wrote:

> I used kubernetes plugin to build a pipeline job, but it need at least 10s
> to create pod since build job. Why?
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/9cb3f4f7-06ba-43ba-8206-1f60b451a8d0%
> 40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NaAyVP0%3D1Bf%3Dgqw50Oi73S_6hZDA-hy-G0dZ9MQ2_ddQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: URI is not hierarchical error running tests in Intellij?

[Carlos Sanchez]

I'm getting the same error in Eclipse, no snapshots nor dependencies 
between eclipse projects

The TestPluginManager.loadBundledPlugins(TestPluginManager.java:117 is 
trying to create a File from url

jar:file:/Users/csanchez/.m2/repository/org/jenkins-ci/plugins/workflow/workflow-step-api/2.3/workflow-step-api-2.3-tests.jar!/test-dependencies/workflow-step-api.jpi

Using jenkins-test-harness 2.15


On Thursday, October 20, 2016 at 2:29:49 PM UTC+2, Jesse Glick wrote:
>
> On Thu, Oct 20, 2016 at 7:32 AM, Andrew Bayer  > wrote: 
> > https://gist.github.com/abayer/57d0c42ee97aa9fe96932c960bbe2d16 
>
> FTR this is a failure to `mvn -DskipTests install` a snapshot 
> dependency. I will see if the message can be made more 
> self-explanatory. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/671875d0-c2f5-4920-9669-b4df31642d49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Release Kubernetes Plugin 0.9

[Carlos Sanchez]

Not sure what happened and I'm traveling at the moment without my laptop,
will have to wait until next week. Sorry

On Thu, Nov 3, 2016, 01:06 Joan G  wrote:

> Thanks Daniel!
>
> On Wednesday, 2 November 2016 15:56:06 UTC, Daniel Beck wrote:
>
>
> > On 02.11.2016, at 16:48, Joan G  wrote:
> >
> > I see in many places that the version 0.9 of the Kubernetes Plugin is
> released.
> > But I can't see the new version actually released on the official page
> and also in the Plugin updates in Jenkins.
>
> Seems the release failed and only created a snapshot build.
>
> I'll inform Carlos.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/110653d7-c37b-44f3-88ec-17f79a1c99e4%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Pd%2B0wWy___whLOJ2jsJ40SBw1dgBw9E%3DrxseiROtFErg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Maven JVM terminated unexpectedly with exit code 137 - Building plugin

[Carlos Sanchez]

IIUC You are hitting the memory limits and the kernel is killing your
process.
You are setting Xmx for surefire to 1GB, you should try lowering it if your
tests don't really need that much memory.
https://github.com/jenkinsci/serenity-plugin/blob/master/pom.xml#L60

On Mon, Jul 4, 2016 at 1:37 PM, Michael Couck 
wrote:

> Hi all,
>
> I am getting the above on the CloudBees build for the Serenity plugin(
> https://jenkins.ci.cloudbees.com/job/plugins/job/serenity-plugin/). I
> have seen this has popped up before, and seemingly it is a memory issue.
> Unfortunately I don't have access to the job to increase the memory to see.
> Could I get a little more memory please? Pretty please? ;) Perhaps 1024?
>
> The build is quite memory intensive in fact, exactly how much I wouldn't
> know, but on my Jenkins I run the build with a gig, and that seems to be
> enough. Of course the build works perfectly on my laptop, and on my server
> running Jenkins, with the above memory parameters. Could be something else
> of course, but for the life of me I can't imagine what. The jdk is the
> same, and even the os is the same. There is some classloading interference,
> but it is in a forked JVM so should be quite safe.
>
> Incidentally the build was running fine until I started fiddling around
> with the profiler again...
>
> Sorry for the bother :( but I am stuck.
>
> Cheers,
> Michael
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/8187fb6d-1fc2-48c8-ba6e-5f136ee78106%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PPKEUxHoPBhrHgAQ%3D5p4KwF-MvB_6RvsODxRshYC-GKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Docker image security scan

[Carlos Sanchez]

Hi, 

The last docker image for 1.651.3 is up in the docker hub.

The official images are now security scanned, and you can see the results 
at https://hub.docker.com/r/library/jenkins/tags/1.651.3/ (need to be 
logged in)

Some layers come from the parent Debian and Java images, but the last ones 
are from Jenkins war, showing several CVEs for Spring (critical), Groovy 
(critical), httpclient, commons-compress, xstream and jbcrypt

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/caf20fac-70d0-4429-8335-ed3366105982%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: kubernetes plugin version 0.4 and repo.jenkins-ci.org

[Carlos Sanchez]

I could cut a release this weekend with the latest changes from Nicolas

On Friday, October 2, 2015 at 3:23:45 PM UTC+2, Oleg Nenashev wrote:
>
> Hi Gabe,
>
> If you are asking about something plugin-related, it's recommended to add 
> its maintainers to Cc.
>
> Best regards,
> Oleg
>
> вторник, 29 сентября 2015 г., 17:57:17 UTC+3 пользователь Gabe Montero 
> написал:
>>
>> Sorry, yes that is the point ;-)   I was curious if the release date for 
>> 0.4 was known yet, and if so, could it be revealed to the public at this 
>> time?
>>
>> thanks
>>
>> On Tuesday, September 29, 2015 at 10:22:16 AM UTC-4, Daniel Beck wrote:
>>>
>>> I'm not sure what you're asking. 0.4 hasn't been released yet. 
>>>
>>> On 29.09.2015, at 16:09, Gabe Montero  wrote: 
>>>
>>> > Does anybody know when the latest kubernetes-plugin version available 
>>> on repo.jenkins-ci.org will be bumped from 0.3 to 0.4? 
>>> > 
>>> > thanks, 
>>> > gabe 
>>> > 
>>> > -- 
>>> > 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-de...@googlegroups.com. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/71eeab04-4094-4cf7-b771-acd2c3e68988%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2ce6d68c-d356-40cd-aefe-5a559f09100f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

EOFException when terminating slaves programatically

[Carlos Sanchez]

Hi,

While writing the Kubernetes plugin, a plugin to dynamically start slaves 
in Kubernetes (something similar to the Docker one) I am getting 
EOFException when deleting the Pod (the container running the jenkins-slave 
jar)

The code for _terminate

cloud.connect().deletePod(name, cloud.getNamespace());
LOGGER.log(Level.INFO, Terminated Kubernetes instance for 
slave {0}, name);
toComputer().disconnect(OfflineCause.create(new 
Localizable(HOLDER, offline)));
LOGGER.log(Level.INFO, Disconnected computer {0}, name);

https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L75

I have tried in the reverse order, disconnect, then deletePod with the same 
result, even adding a sleep() call between both
I'm not sure what am I missing, if I should call something else to close 
the slave connection


Aug 26, 2015 4:19:17 PM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate
INFO: Terminating Kubernetes instance for slave 
f911b094-2674-4645-b066-f28726e4b3d8
Aug 26, 2015 4:19:17 PM hudson.remoting.AbstractByteArrayCommandTransport$1 
handle
WARNING: Failed to construct Command
java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2328)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2797)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
at java.io.ObjectInputStream.init(ObjectInputStream.java:299)
at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40)
at 
hudson.remoting.AbstractByteArrayCommandTransport$1.handle(AbstractByteArrayCommandTransport.java:61)
at org.jenkinsci.remoting.nio.NioChannelHub$2.run(NioChannelHub.java:594)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


Thanks in advance

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/33c4d0ec-9116-4a1d-b6f1-827081131f2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for Kubernetes plugin

[Carlos Sanchez]

Thanks!

On Mon, Feb 16, 2015 at 10:03 AM, nicolas de loof nicolas.del...@gmail.com
wrote:

 ok got it - I deleted and re-forked from correct location

 2015-02-16 10:01 GMT+01:00 nicolas de loof nicolas.del...@gmail.com:

 https://github.com/jenkinsci/kubernetes-plugin says forked from
 carlossg/kubernetes-jenkins
 https://github.com/carlossg/kubernetes-jenkins

 is there anything to fix ?

 2015-02-16 9:19 GMT+01:00 Carlos Sanchez car...@apache.org:

 I'm sure some user will get confused with the forked from in github.
 If somebody can delete it it would be better, otherwise I'll do that.

 On Saturday, February 14, 2015 at 5:31:42 PM UTC+1, Kanstantsin Shautsou
 wrote:

 What is the problem to force push right content?

 On Wednesday, February 11, 2015 at 4:10:11 PM UTC+3, Carlos Sanchez
 wrote:

 Hi,

 I'd like to get the Kubernetes plugin under jenkinsci org, with the
 automated builds, deployments, etc.

 It is currently at https://github.com/carlossg/
 jenkins-kubernetes-plugin and my github id is carlossg

 On IRC Arnaud tried to do it but I gave hime the wrong repo (facepalm)
 and he didn't have permissions to drop it, so now there's this
 https://github.com/jenkinsci/kubernetes-plugin that needs to be
 dropped before.

 Thanks

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/a678589b-9cec-489b-b815-06e9a1ac84bd%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/a678589b-9cec-489b-b815-06e9a1ac84bd%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.



  --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Developers group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/fJJ0ynLzThA/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznftO2-KDNbu0%2BCA21oj9h53kq2ovsQEhN7L3PENPsr3Q%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznftO2-KDNbu0%2BCA21oj9h53kq2ovsQEhN7L3PENPsr3Q%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NGvuUwktTAT8O0EKQNrn%3Dp8mhAbN6F%2Bz4GtoHbM0hw%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for Kubernetes plugin

[Carlos Sanchez]

I'm sure some user will get confused with the forked from in github.
If somebody can delete it it would be better, otherwise I'll do that.

On Saturday, February 14, 2015 at 5:31:42 PM UTC+1, Kanstantsin Shautsou 
wrote:

 What is the problem to force push right content?

 On Wednesday, February 11, 2015 at 4:10:11 PM UTC+3, Carlos Sanchez wrote:

 Hi,

 I'd like to get the Kubernetes plugin under jenkinsci org, with the 
 automated builds, deployments, etc.

 It is currently at https://github.com/carlossg/jenkins-kubernetes-plugin 
 and my github id is carlossg

 On IRC Arnaud tried to do it but I gave hime the wrong repo (facepalm) 
 and he didn't have permissions to drop it, so now there's this 
 https://github.com/jenkinsci/kubernetes-plugin that needs to be dropped 
 before.

 Thanks



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a678589b-9cec-489b-b815-06e9a1ac84bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Request hosting for Kubernetes plugin

[Carlos Sanchez]

Hi,

I'd like to get the Kubernetes plugin under jenkinsci org, with the 
automated builds, deployments, etc.

It is currently at https://github.com/carlossg/jenkins-kubernetes-plugin 
and my github id is carlossg

On IRC Arnaud tried to do it but I gave hime the wrong repo (facepalm) and 
he didn't have permissions to drop it, so now there's this 
https://github.com/jenkinsci/kubernetes-plugin that needs to be dropped 
before.

Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d5f36016-1ece-4e7c-a1aa-fba8dc82354e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kubernetes plugin advice

[Carlos Sanchez]

Hi!

I'm creating the Kubernetes plugin [1] to start slaves in Kubernetes or 
Google Container Engine, which basically means launching Docker containers 
across multiple hosts with just one API.
Some background: Kubernetes allows launching individual containers (Pods) 
or creating a ReplicationController, which accepts a Pod template and a 
number of how many containers you want to run, and can be resized 
dynamically, a pool of containers.

Initially I though about implementing the plugin using a 
ReplicationController and resizing it as new slaves are needed, but seems 
that Jenkins operation doesn't fit well with this idea. It would prevent 
killing specific slaves, it would just be a pool. So I went ahead and moved 
to launch Pods one by one.

The issue I have now is about initialization time, where the container is 
not accepting connections until the image is downloaded and started. The 
Docker plugin has this comment [2]

// Docker instances may have a long init script. If we declare
// the provisioning complete by returning without the connect
// operation, NodeProvisioner may decide that it still wants
// one more instance, because it sees that (1) all the slaves
// are offline (because it's still being launched) and
// (2) there's no capacity provisioned yet.
//
// deferring the completion of provisioning until the launch
// goes successful prevents this problem.
slave.toComputer().connect(false).get();

Should I do the same?

There is also the issue that Kubernetes would be better suited for swarm 
slaves. Opening ssh or ports in each pod is more complicated than just 
doing the connection to the master from the container.

Thanks!

[1] 
https://github.com/carlossg/jenkins-kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java
[2] 
https://github.com/jenkinsci/docker-plugin/blob/master/src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java#L239

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5e641038-b83b-4901-83a8-4bb54255498a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.