[JIRA] (JENKINS-42369) agent docker parameters do not honor the current environment

[sven.carstens@udg.de (JIRA)]

Sven Carstens created an issue

Jenkins / JENKINS-42369 agent docker parameters do not honor the current environment Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Feb/28 10:40 AM Priority: Minor Reporter: Sven Carstens Currently I need to use multiple docker containers which need to be linked together. I tried using the --link option to set the linked image. In my use-case I don't want to set a fixed name but need to use a variable for the name. In this case the args parameter is evaluated to "--link null:linkedimage" and the job fails. Or is there another way to pass dynamic parameters (from variables) to the docker args? pipeline { agent any environment { LINK_DOCKER_IMAGE = "linkedimage" } stages { stage ('Compose') { agent { docker { image 'alpine' args "--link ${env.LINK_DOCKER_IMAGE}:linkedimage" } } steps { sh 'printenv' } } } } Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[gdupin@gmail.com (JIRA)]

Guillaume Dupin commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment Hi ! This bug is very troubelsome for us and the workarounds does not work in all cases... and are workarounds Would it be possible to change the priority to accelerate the fix please ?

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[gdupin@gmail.com (JIRA)]

Guillaume Dupin updated an issue

Jenkins / JENKINS-42369

agent docker parameters do not honor the current environment

Change By: Guillaume Dupin Comment: Hi ! This bug is very troubelsome for us and the workarounds does not work in all cases... and are workarounds ;)

Would it be possible to change the priority to accelerate the fix please ?

Add Comment

[gdupin@gmail.com (JIRA)]

Guillaume Dupin commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment Hi ! This bug is very troubelsome for us and the workarounds does not work in all cases... and are workarounds

Would it be possible to change the priority to accelerate the fix please ?

Add Comment

[vlassov@magnum.kz (JIRA)]

Anatoliy Vlassov commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment

Same issue. I am using a dockerfile agent and there is no way (or I don't know one) to pass environment variables to the "docker build" command. Example: pipeline { environment { SSH_KEY = credentials('ssh-key') } agent { dockerfile { additionalBuildArgs "--build-arg SSH_KEY=${SSH_KEY}" } } stages { stage('Test') { steps { sh 'go test' } } } }

Add Comment

[vfratila@adobe.com (JIRA)]

Vlad Fratila commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment

It would be great for env vars to work with env vars.

Add Comment

[Jorge.w.machado@hotmail.com (JIRA)]

Jorge Machado commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment

I have another use case for this. Running builds with nvidia-docker we need to pass NV_GPU= 0,1 at container start ... This does not work with the environment directive

Add Comment

[philippjung2010@live.de (JIRA)]

Philipp Jung commented on JENKINS-42369

Re: agent docker parameters do not honor the current environment

Same issue here. Any chance to change the priority?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)