Re: jenkins official kubernetes operator

Hi all, It's been a while. I've just submitted abstract for Jenkins World 2019 in Lisbon. My reference number is JNXM6DMR0M. Could someone check if everything is ok with it? We've gathered a lot of feedback from the community. I think we are close to promote the project to beta. Regards,

Re: jenkins official kubernetes operator

I created the repository jenkins4eval/kubernetes-operator and gave admin permission to tomasz cfr [INFRA-2013 ] Once this docker image is considered as

Re: jenkins official kubernetes operator

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

Re: jenkins official kubernetes operator

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

Re: jenkins official kubernetes operator

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

Re: jenkins official kubernetes operator

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

Re: jenkins official kubernetes operator

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

Re: jenkins official kubernetes operator

Hi all, How can I request new docker hub repository "jenkins/kubernetes-operator"? 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

Re: jenkins official kubernetes operator

Hi, I would prefer fork. Regards, Tomasz niedz., 10 lut 2019, 12:20: Oleg Nenashev napisał(a): > Hi, > > Thanks for doing it! Would you prefer the repo to be forked or moved? The > process is slightly different > > On Sun, Feb 10, 2019, 12:14 Tomasz Sęk wrote: > >> >> Hi all, >> >> My JEP

Re: jenkins official kubernetes operator

Hi, Thanks for doing it! Would you prefer the repo to be forked or moved? The process is slightly different On Sun, Feb 10, 2019, 12:14 Tomasz Sęk wrote: > > Hi all, > > My JEP has been approved as a Draft so I've raised JIRA ticket to fork > jenkins-operator to jenkinsci organization

Re: jenkins official kubernetes operator

Hi all, My JEP has been approved as a Draft so I've raised JIRA ticket to fork jenkins-operator to jenkinsci organization HOSTING-708 . Best regards, Tomasz -- You received this message because you are subscribed to the Google Groups

Re: jenkins official kubernetes operator

Hi all, I've created PR with JEP. Best 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

Re: jenkins official kubernetes operator

On Friday, 25 January 2019 19:26:41 UTC+1, Jesse Glick wrote: > > >>> we have to run some jobs on master to configure it(apply groovy > scripts, restore/backup and seed jobs creation). > > > >> This seems inadvisable and is generally insecure. Better for these > tasks to be externalized. > >

Re: jenkins official kubernetes operator

On Fri, Jan 25, 2019 at 8:51 AM Tomasz Sęk wrote: > We had a lot of issues when Kubernetes coudn't detach PVC after pod restart > and the new one coudn't be loaded. I see. Thanks for clearing this up. >>> we have to run some jobs on master to configure it(apply groovy scripts, >>>

Re: jenkins official kubernetes operator

On Friday, 25 January 2019 04:35:05 UTC+1, 夏润泽 wrote: >> Making backup of ~50GB is not good idea. I don't want to make snowflake. When new Jenkins master comes up it should starts with empty `$JENKINS_HOME` and jenkins-operator have to configure it to desire >> state. Backup is triggered

Re: jenkins official kubernetes operator

On Thursday, 24 January 2019 20:41:02 UTC+1, Jesse Glick wrote: >> make backup of jobs history before Jenkins master pod deletion and restore it in new pod >> You do not just set a custom build record directory […] and use a persistent volume claim? […] >> Beware however that there is some

Re: jenkins official kubernetes operator

> > Making backup of ~50GB is not good idea. I don't want to make snowflake. > When new Jenkins master comes up it should starts with empty > `$JENKINS_HOME` and jenkins-operator have to configure it to desire state. > Backup is triggered before Jenkins master pod deletion and it have to be >

Re: jenkins official kubernetes operator

On Thu, Jan 24, 2019 at 11:32 AM Tomasz Sęk wrote: >>> make backup of jobs history before Jenkins master pod deletion and restore >>> it in new pod > >> You do not just set a custom build record directory […] and use a persistent >> volume claim? […] >> Beware however that there is some more

Re: jenkins official kubernetes operator

> > > > I forgot to mention that plugins are separated in two groups: required by > jenkins-operator(used to configure Jenkins)(A) and required by user(B). > A: > - they are installed by jenkins-operator before Jenkins can start up > - every single change requires restart of Jenkins master

Re: jenkins official kubernetes operator

On Wednesday, 23 January 2019 16:06:03 UTC+1, Jesse Glick wrote: > It sounds nice (I have not tried it). Some technical questions / comments: > make backup of jobs history before Jenkins master pod deletion and restore it in new pod > You do not just set a custom build record directory (IIRC

Re: jenkins official kubernetes operator

Sounds great, I can help the JEP process. On Wednesday, January 23, 2019 at 10:16:25 PM UTC+8, Tomasz Sęk wrote: > > Hi all, > > My name is Tomasz Sęk and I work in Virtuslab company > as a senior DevOps engineer. I'm the main maintainer of >

Re: jenkins official kubernetes operator

It sounds nice (I have not tried it). Some technical questions / comments: On Wed, Jan 23, 2019 at 9:16 AM Tomasz Sęk wrote: > every single plugin and it's depended plugins have to be installed with > specific version Good, I have long fought against plugin management scripts/tools which try

Re: jenkins official kubernetes operator

Hi all, My name is Tomasz Sęk and I work in Virtuslab company as a senior DevOps engineer. I'm the main maintainer of https://github.com/VirtusLab/jenkins-operator project. We've been provide Jenkins for customers(programmer teams) in our custom Kubernetes distribution

Re: jenkins official kubernetes operator

I have checked this repo, I think some of the function points are coincident, such as the integration of CasC. But the final features may not be consistent, perhaps we should discuss their ideas about the operator? On Monday, January 21, 2019 at 2:34:01 PM UTC+8, nicolas de loof wrote: > > Have

Re: jenkins official kubernetes operator

Have you checked overlap with https://github.com/VirtusLab/jenkins-operator ? I was discussing with the authors to get this contributed in jenkinsci organization. Should avoid a concurrent effort to happen on same topic. Le lun. 21 janv. 2019 à 05:54, Rick a écrit : > I'm in > > On Monday,

Re: jenkins official kubernetes operator

I'm in On Monday, January 21, 2019 at 6:44:11 AM UTC+8, marky.r...@gmail.com wrote: > > 夏润泽 and I started documenting this JEP and initial code. If anyone is > interested in helping let us know. > > On Sunday, January 20, 2019 at 5:55:45 AM UTC-8, 夏润泽 wrote: >> >> I also think that creating a

Re: jenkins official kubernetes operator

夏润泽 and I started documenting this JEP and initial code. If anyone is interested in helping let us know. On Sunday, January 20, 2019 at 5:55:45 AM UTC-8, 夏润泽 wrote: > > I also think that creating a prototype is a good suggestion, we can > contact on gitter > > On Sunday, January 20, 2019 at

Re: jenkins official kubernetes operator

I also think that creating a prototype is a good suggestion, we can contact on gitter On Sunday, January 20, 2019 at 8:05:51 PM UTC+8, Marky Jackson wrote: > > I agree that creating a prototype is the best path forward. > We can split the work up for documenting that yaml format and the cli >

Re: jenkins official kubernetes operator

I agree that creating a prototype is the best path forward. We can split the work up for documenting that yaml format and the cli options. I will wait to hear from RunzeXia and we can have further discussion (please reach out to me on gitter or via email). Thanks kindly. { "regards" : {

Re: jenkins official kubernetes operator

Hi all, After reading the proposal from RunzeXia in this pull request , I think that the official Kubernetes Operator could be built on the top of the Custom WAR/Docker Packager which

Re: jenkins official kubernetes operator

Who/how can we go about starting this? I will gladly upload my code but it might be best to have some guidelines or plan On Thursday, January 17, 2019 at 9:25:27 PM UTC-8, 夏润泽 wrote: > > Very good, I think we can start working from your operator > > On Wednesday, January 16, 2019 at 12:42:38 AM

Re: jenkins official kubernetes operator

Very good, I think we can start working from your operator On Wednesday, January 16, 2019 at 12:42:38 AM UTC+8, Marky Jackson wrote: > > I’ve done some current operator work and have submitted an upcoming talk > on operators. > I would love to even just tinker with this idea > > { >

Re: jenkins official kubernetes operator

I guess you might be interested by https://github.com/VirtusLab/jenkins-operator Le jeu. 17 janv. 2019 à 15:06, 夏润泽 a écrit : > 非常好，我想我们可以从您的运营商开始工作 > > 周一，2019年1月16日星期三上午12:42:38 UTC + 8，Marky Jackson写道： >> >> 我已完成了一些当前的操作员工作，并提交了关于操作员的即将到来的演讲。 >> 我很想甚至只是修补这个想法 >> >> { >>“问候”：{ >>

Re: jenkins official kubernetes operator

Recently there are a lot of things in the company, I will submit relevant PR on the weekend. On Wednesday, January 16, 2019 at 12:38:24 AM UTC+8, Jesse Glick wrote: > > On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 > > wrote: > > we could use the k8s jenkins operator to do more things, such as the >

Re: jenkins official kubernetes operator

I’ve done some current operator work and have submitted an upcoming talk on operators. I would love to even just tinker with this idea { "regards" : { "name" : “marky”, "phone" : "+1 (408) 464 2965”, "email" : “marky.r.jack...@gmail.com", "team" :

Re: jenkins official kubernetes operator

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 wrote: > we could use the k8s jenkins operator to do more things, such as the health > status of jenkins (whether the configuration is consistent and the necessary > components are normal)、 automatic update based on Jenkins Evergreen… There is nothing being

Re: jenkins official kubernetes operator

Jenkins of serverless cannot meet my needs at present, but I have to say that when it becomes more perfect, it will be a very cool features. On Tuesday, January 15, 2019 at 4:17:19 PM UTC+8, Carlos Sanchez wrote: > > I thought about it, and yes it would be interesting to have an operator > that

Re: jenkins official kubernetes operator

CasC support observer mode is a very powerful and useful function. But we could use the k8s jenkins operator to do more things, such as the health status of jenkins (whether the configuration is consistent and the necessary components are normal)、 automatic update based on Jenkins

Re: jenkins official kubernetes operator

Introducing a watcher to reload changes has been proposed for Configuration-as-Code: https://github.com/jenkinsci/configuration-as-code-plugin/issues/76 just need to be implemented ... Le mar. 15 janv. 2019 à 09:17, Carlos Sanchez a écrit : > I thought about it, and yes it would be interesting

Re: jenkins official kubernetes operator

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]

jenkins official kubernetes operator

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