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: Press contact in China

As discussed before, I totally support it. Thanks a lot, Rick! If there are any major queries and discussions happening via press contacts, it would be great to receive some summaries (user feedback, links to articles in Chinese, etc.), e.g. in the Advocacy & Outreach mailing list. It would

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: Press contact in China

> > If there are any major queries and discussions happening via press > contacts, it would be great to receive some summaries (user feedback, links > to articles in Chinese, etc.), e.g. in the Advocacy & Outreach mailing > list. It would help us to adjust messaging we do in the Jenkins community.

Jenkins build from source broken

Hi, mvn install stopped working within the last 24 hours. I did a clean download, tried and saw the following error: mvn install -DskipTests ... [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO]

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: [Plugin adoption] groovy-events-listener-plugin

Sorry for the lack of answers here. I'm going to proceed here, because of the latency, despite you missed a critical step AFAICT in our process https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess : putting the previous maintainer(s) in CC... Le dim. 20

Re: [Plugin adoption] groovy-events-listener-plugin

Done! You should have received an invitation. Welcome aboard! [21:03] <+ batmat> | jenkins-admin: make jequals5 committer of groovy-events-listener-plugin [21:03] <@jenkins-adm> | Failed to add user to team: {"message":"Not Found","documentation_url":"

Re: [Plugin adoption] groovy-events-listener-plugin

Thank you for that. No sooner did I start to do work I also lost access. It appears my access has been revoked { "regards" : { "name" : “marky”, "phone" : "+1 (408) 464 2965”, "email" : “marky.r.jack...@gmail.com", "team" : "jackson5“ } } > On Jan 20,

Re: [Plugin adoption] groovy-events-listener-plugin

:-( man I am so frustrated. As I sent in a few private messages in Gitter, any help is greatly appreciated I pay in beer, burritos or other San Francisco funs during the next Jenkins World. I am just trying to chop wood and carry water On Sunday, January 20, 2019 at 12:44:05 PM UTC-8, Marky

Re: Jenkins build from source broken

You are correct, I retried recently and it passed. I guess the remote repo was down or unreachable. On Sunday, January 20, 2019 at 11:59:42 AM UTC-8, Baptiste Mathus wrote: > > Yeah, that is weird, also happened on CI since very recently on the latest > master. Likely a temporary network

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 build from source broken

Yeah, that is weird, also happened on CI since very recently on the latest master. Likely a temporary network glitch, you likely want to just retry. I created https://github.com/jenkinsci/jenkins/pull/3856 to retry, but FYI I tested also locally and it succeeded. Cheers Le dim. 20 janv. 2019 à

Re: [Plugin adoption] groovy-events-listener-plugin

It appears the admin team has disappeared { "regards" : { "name" : “marky”, "phone" : "+1 (408) 464 2965”, "email" : “marky.r.jack...@gmail.com", "team" : "jackson5“ } } > On Jan 20, 2019, at 12:05 PM, Baptiste Mathus wrote: > > Done! You should

Re: [Plugin adoption] groovy-events-listener-plugin

Hi Marky, I have restored the team and granted it Write permissions. Due to whatever reason, the team was just disconnected from the repo. AFAICT, our ChatOps bot also needs update to fix group permission assignments. Now it sets "Read" instead of "Write" upon creation. As I sent in a few

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

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,