-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
CloudBees Docker Workflow 1.2
Jenkins ver. 1.625.3.1 (CloudBees Jenkins Enterprise 15.11)
sshagent('my-ssh-key'){...} is ignored in docker.image('cloudbees:java-build-tools').inside{...}. The same sshagent step works in 'standard' linux node.
See attached logs
sshagent(){...} ignored in docker.image(...).inside{...}
docker.image ('cloudbees/java-build-tools:0.0.7.1').inside { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } }
sshagent(){...} WORKS in node{...}
node { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } }
- duplicates
-
JENKINS-27152 Store sh control files outside of workspace
-
- Resolved
-
- is related to
-
JENKINS-42582 ssh-agent not applied in kubernetes container
-
- Resolved
-
[JENKINS-32624] sshagent{} ignored when executed in docker.image().inside{...}
Environment |
New:
CloudBees Docker Workflow 1.2 Jenkins ver. 1.625.3.1 (CloudBees Jenkins Enterprise 15.11) |
Description |
Original:
{{sshagent(...)\{...\}}} is ignored in {{docker.image(...).inside\{...\}}}. The same sshagent step works in 'standard' linux node. See attached logs {code:title=sshagent()\{...\} ignored in docker.image(...).inside\{...\} } docker.image ('cloudbees/java-build-tools:0.0.7.1').inside { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } } {code} {code:title=sshagent()\{...\} WORKS in node\{...\} } node { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } } {code} |
New:
{{sshagent('my-ssh-key')\{...\}}} is ignored in {{docker.image('cloudbees:java-build-tools').inside\{...\}}}. The same sshagent step works in 'standard' linux node. See attached logs {code:title=sshagent()\{...\} ignored in docker.image(...).inside\{...\} } docker.image ('cloudbees/java-build-tools:0.0.7.1').inside { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } } {code} {code:title=sshagent()\{...\} WORKS in node\{...\} } node { sh 'ls -al ~/.ssh/ || true' sshagent(['aws-cleclerc-ssh-key-ubuntu-cleclerc']) { sh 'echo SSH_AUTH_SOCK=$SSH_AUTH_SOCK' sh 'ls -al $SSH_AUTH_SOCK || true' sh "ssh -vvv -o StrictHostKeyChecking=no ubuntu@docker-agent.beesshop.org uname -a" } } {code} |
Link |
New:
This issue depends on |
Component/s | New: ssh-agent-plugin [ 17509 ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
Original:
This issue depends on |
Link |
New:
This issue is related to |
Link |
Original:
This issue is related to |
Comment |
[ I'm having the exact same issue if the script is executed via Jenkinsfile with the GitHub Organisation Plugin. Same script copied into a Pipeline Job works. It works while using Jenkinsfile and using node{} instead of docker.image.inside. Jenkins: 2.7.1 LTS SSH Agent Plugin: 1.13 ] |