Re: Regarding docker : JENKINS-30113

2015-11-01 Thread Irfan Sayed
Thanks Nicolas. Let me try 1.6.4 right away and explore will update soon Regards Irfan On Mon, Nov 2, 2015 at 12:04 PM, nicolas de loof wrote: > Hi, > > cloudbees docker custom build environment 1.6.x branch is focussing on evn > issues, especially considering > - we don't want docker host sla

Re: Regarding docker : JENKINS-30113

2015-11-01 Thread nicolas de loof
Hi, cloudbees docker custom build environment 1.6.x branch is focussing on evn issues, especially considering - we don't want docker host slave env to pollute the container one - we want env defined by Docker image / Dockerfile to be available for the build - we want buildwrappers to be able to in

Re: Regarding docker : JENKINS-30113

2015-11-01 Thread Irfan Sayed
Thanks Jason. OK. let me in detail out all steps which i carried out. Created Dockerfile (PFA). Created Jenkins Job which will is connected to one UNIX box (using ssh port : 22) on which docker daemon is running as a part of Jenkins job configuration, i choose the option "Build inside a Docker con

Re: Regarding docker : JENKINS-30113

2015-11-01 Thread Jason Swager
If you're using the Docker plugin (https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin), I found the env vars worked fine when they were setup to be available to incoming .ssh connections. That sometimes meant using a different config file within the container to prep the variables. A g

Fwd: Regarding docker : JENKINS-30113

2015-11-01 Thread Irfan Sayed
further update: after lot of digging, i found that whatever environment variables set in Dockerfile (actually in image created using this dockerfile) are not available in build section using docker plugin . but in reality , we need these variables to be available in the build section. In typical u

Re: jenkin job executing selenium scripts twice

2015-11-01 Thread Yonnatan bar
Please Post your Job Configuration On Tuesday, October 27, 2015 at 6:51:02 AM UTC+2, Siva Rakesh wrote: > > Observed that selenium test scripts are executed twice each time when > triggered the jnkins build job. > > Any idea? please help me. > > Thanks, > -- You received this message because

Re: Access BUILD_CAUSE and BUILD_CAUSE_USERIDCAUSE through Build Flow DSL

2015-11-01 Thread GS_L
The problem is that the EnvInject isn't enabled through the BuildFlow. On Thursday, October 29, 2015 at 10:15:58 PM UTC+2, Martin d'Anjou wrote: > > Been asking myself the same question for 3 years. The only solution for me > is to use EnvInject, fetch the cause from the Jenkins internal objects,