-
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
-
Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/com/cloudbees/jenkins/plugins/sshagent/RemoteAgentFactory.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/SSHAgentBuildWrapper.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/SSHAgentStepExecution.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/JNRRemoteAgent.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/JNRRemoteAgentFactory.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/JNRRemoteAgentStarter.java
src/main/java/com/cloudbees/jenkins/plugins/sshagent/mina/MinaRemoteAgentFactory.java
http://jenkins-ci.org/commit/ssh-agent-plugin/d2e0f53b6eda56012c2bd5d9bc553b31667462a2
Log:
JENKINS-32624JENKINS-27152Use a standardized temporary directory when possible.