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

Is the only purpose of the parameter/property to differentiate between the devtest/oat/prod? If that's the case, can you use ${env.JOB_NAME} ? On Friday, August 24, 2018 at 10:47:14 AM UTC-5, Adam Hardy wrote: > > Hi > > I'd like my Jenkins multi-branch and pipeline jobs to pass in a >

Re: JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

Does the pod template meet the Kubernetes plugin constraints mentioned in readme? Specifically, is ttyEnabled and is there a long-running process that will allow the pod to continue running until the job completes? On Sat, Aug 25, 2018

JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

I'm using Kubernetes plugin 1.12.3 The plugin works well, but whenever the agent does streams the log to the master, it causes a connection exception as follows. To reproduce, simply create a free style job, restrict to run on the kubernetes pod, and add a step to sleep for 300 seconds.

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

If you set the number of executors on both master and slave to 1 that will restrict the number of builds to one per node put a third into the queue. Regards Daniel On Fri, 24 Aug 2018, 12:58 Nati Mirauta, wrote: > Hello, > > I would like to know if there is a way to run a job on master once