Some issues with env vars with kubernetes plugin declarative (1.6.0 and 1.9.2)

Hello, I'm waiting for your feedback before opening a bug for information I have seen this SO post : https://stackoverflow.com/questions/45372798/jenkins-kubernetes-plugin-not-passing-environment-variables-with-pipeline and some others but I can't figure out why it is not working My jenkins c

Volume issue with kubernetes plugin in declarative way (1.6.0 and 1.9.2)

Hello in my jenkins configuration admin GUI I have this volume definition : Volumes - Claim Name = nfsdata Read Only = true Mount path = /etc/ssl/certs In scripted pipeline everything works perfectly In declarative pipeline : pipeline { agent { kubernetes { label "${jedi}" yaml """ spec: cont

Configuration-as-Code 1.0-RC2 released

Not a long time ago Nicolas De Loof announced we've release Configuration-as-Code 1.0-RC1. I'm happy to inform you Configuration-as-Code 1.0-RC2 is out now, we've: - Introduced functionality to replace existing configuration via UI. - Re-introduced support for 'latest' version when installi

Re: Configuration-as-Code 1.0-RC2 released

Any plan to support to read configuration from git? On Fri, Aug 24, 2018 at 5:06 PM Ewelina Wilkosz wrote: > Not a long time ago Nicolas De Loof announced we've > release Configuration-as-Code 1.0-RC1. > I'm happy to inform you Configuration-as-Code 1.0-RC2 is out now, we've: > >- Introduced

Re: Volume issue with kubernetes plugin in declarative way (1.6.0 and 1.9.2)

On Fri, Aug 24, 2018 at 10:42 AM Tristan FAURE wrote: > Hello > > in my jenkins configuration admin GUI I have this volume definition : > > Volumes > - Claim Name = nfsdata > Read Only = true > Mount path = /etc/ssl/certs > > In scripted pipeline everything works perfectly > > In declarative pipe

Re: Volume issue with kubernetes plugin in declarative way (1.6.0 and 1.9.2)

Le ven. 24 août 2018 à 11:09, Carlos Sanchez a écrit : > > > On Fri, Aug 24, 2018 at 10:42 AM Tristan FAURE > wrote: > >> Hello >> >> in my jenkins configuration admin GUI I have this volume definition : >> >> Volumes >> - Claim Name = nfsdata >> Read Only = true >> Mount path = /etc/ssl/certs >

Re: Some issues with env vars with kubernetes plugin declarative (1.6.0 and 1.9.2)

1 and 2 should work for sure, we have a test for env vars https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugins/kubernetes/pipeline/runWithEnvVars.groovy On Fri, Aug 24, 2018 at 10:27 AM Tristan FAURE wrote: > Hello, > I'm waiting for your

Re: Configuration-as-Code 1.0-RC2 released

yes, we already support url as a configuration location, so we kind of support e.g. github, just use raw link, like in example: https://raw.githubusercontent.com/[repo]/master/jenkins.yaml in the future we want to support git - it is not designed yet, but I have a plan :) so git repo + branch

Re: Some issues with env vars with kubernetes plugin declarative (1.6.0 and 1.9.2)

With Scripted pipeline we have no problem. It occurs with declarative Le ven. 24 août 2018 à 11:14, Carlos Sanchez a écrit : > 1 and 2 should work for sure, we have a test for env vars > > > https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugin

Re: Volume issue with kubernetes plugin in declarative way (1.6.0 and 1.9.2)

On Fri, Aug 24, 2018 at 11:14 AM Tristan FAURE wrote: > > > Le ven. 24 août 2018 à 11:09, Carlos Sanchez a écrit : > >> >> >> On Fri, Aug 24, 2018 at 10:42 AM Tristan FAURE >> wrote: >> >>> Hello >>> >>> in my jenkins configuration admin GUI I have this volume definition : >>> >>> Volumes >>> -

Re: Configuration-as-Code 1.0-RC2 released

Great, if no one does this, I'd like to give it a try. On Fri, Aug 24, 2018 at 5:19 PM Ewelina Wilkosz wrote: > yes, > > we already support url as a configuration location, so we kind of support > e.g. github, just use raw link, like in example: > > https://raw.githubusercontent.com/[repo]/maste

Re: Volume issue with kubernetes plugin in declarative way (1.6.0 and 1.9.2)

OK it makes sense, thank you for the answer Le ven. 24 août 2018 à 11:20, Carlos Sanchez a écrit : > > > On Fri, Aug 24, 2018 at 11:14 AM Tristan FAURE > wrote: > >> >> >> Le ven. 24 août 2018 à 11:09, Carlos Sanchez a >> écrit : >> >>> >>> >>> On Fri, Aug 24, 2018 at 10:42 AM Tristan FAURE >

Re: Configuration-as-Code 1.0-RC2 released

nice! feel free :) I don't think anyone started yet On Friday, August 24, 2018 at 11:20:58 AM UTC+2, su suren wrote: > > Great, if no one does this, I'd like to give it a try. > > On Fri, Aug 24, 2018 at 5:19 PM Ewelina Wilkosz > wrote: > >> yes, >> >> we already support url as a configuration lo

Re: Load balanced Jenkins?

Hi Am Donnerstag, 23. August 2018 19:30:54 UTC+2 schrieb Peter Berghold: > > I've been messing about a bit with Docker on Digital Ocean and was going > to branch next onto Docker Swarm stuff. I was wondering about deploying > Jenkins into a swarm and using a load balancer to switch between ins

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

I wish I could go to Nice :-) I will only be to the San Francisco event. Thanks! Alex On Thu, Aug 23, 2018, 20:08 Mark Waite wrote: > Thanks Slide! > > I'll include you on those topics. I assume San Francisco only unless you > tell me that you'll also be in Nice. > > Mark Waite > > On Mon, Aug

Executors for singe job for multiple users

Hi, Greetings for the day, we are using bitbucket +jenkins for triggering a build now it is good like we are creating pr and merge in both cases build is triggered. Now the major problem is i want to run these in parallel like at same time. when i do this it using the same workspace for that b

Reg Executors for master and slave

Hi Greetings of the day My question is multiple users are triggering one job simultaneously but my build is failed because of same workspace then i got to know there is executor option in Jenkins so how could i trigger my build for different executors for different workspace in Jenkins Thanks

[CONCURRENT BUILDS] Run on master, run on slave and then sit in queue

Hello, I would like to know if there is a way to run a job on master once and after another build request, instead of having the job stay in queue I would want the job to run on slave and then after it runs both on master and on slave, after the next build request it will have to sit in queue.

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

I will be attending in San Francisco. > Am 24.08.2018 um 05:07 schrieb Mark Waite : > > Thanks Ulli! Will you be attending in San Francisco, or Nice, or both? > > On Thu, Aug 23, 2018 at 4:41 PM Ullrich Hafner > wrote: >> Am 21.08.2018 um 02:56 schrieb Mark Wai

Need to pull from a tagged gitlab repo.

Slightly strange request perhaps. I have a scripted pipeline job which which pulling Red Hat RPM files from various places and packaging them up into signed yum repos, which it then tars up ready for sending across to an air-gapped system. We also have a bunch of Ansible code, which is checked

Pass in a parameter/property specified by Jenkins job, not user

Hi I'd like my Jenkins multi-branch and pipeline jobs to pass in a pre-defined parameter or property to the build script in the git repo specified. This isn't for user input. I'm trying to improve the capabilities of a microservices-oriented CD pipeline I inherited. I want to set up more or

New Node Setup - Trigger Job afterwards

Hi, is there a way to trigger a job after a new node was setup. We have a job who writes agent secrets to a nfs share. When the new node boots up it will get its secret from this share and connects to the master. Currently we trigger this job manually, but i would like to get this done automati