#WINDOWS JIRA CLIENT CODE#
Linux target-machine 2.6.32-642.6.2.el6.x86_64 #1 SMP Mon Oct 24 10:22: x86_64 x86_64 x86_64 GNU/Linuxĭ:\jenkins\workspace\freestyletest>exit 0 $ D:\Applications\Git\bin\bash.exe -xe C:\Users\win-user\AppData\Local\Temp\2\hudson7861758823746367406.shĮxecRemoteAgent::execProcess - ssh-agent -k Stopped.Īdded a comment - 13:31 Ok, I've understood a bit more by reading the source code and looking up how ssh agents work.īuilding in workspace D:\jenkins\workspace\freestyletest Using credentials usertest-ppk $ cmd /c call C:\Users\win-user\AppData\Local\Temp\2\hudson3324413359897918200.batĭ:\jenkins\workspace\freestyletest>ssh uname -a Exec ssh-agent (binary ssh-agent on a remote machine) This is my new working output, even though it says that my passphrase is incorrect:īuilding in workspace D:\jenkins\workspace\freestyletest Looking for ssh-agent implementation. I chose the MSYS implementations which come for example with Git for Windows. For this I had to add the commands for ssh-agent, ssh-add and ssh to the PATH. Instead of pursuing this further I got the new implementation referenced in another pull request to work. I can only speculate where the error occurs in mina, tomcat native the jdk or ssh-agent-plugin. This happened 100% of the time with the latest 1.2 and 1.1 versions of tomcat native lib. I think mina crashed when using the tomcat native library. Then no matter what I tried, it failed when actually trying the connection to the opened authentication socket. When executing the released 1.13 version of the plugin even with a more up-to-date jenkins version 2.19.1, it seems to continue with the correct PATH settings and some private key format. Ok, I've understood a bit more by reading the source code and looking up how ssh agents work. Passphrase for key "imported-openssh-key":ĬLINK č:\jenkins\workspace\freestyletest>exit 0 Stopped. Using credentials test-ppk $ cmd /c call C:\Users\tcbld1\AppData\Local\Temp\2\hudson7374457953271842666.batĬLINK č:\jenkins\workspace\freestyletest>E:\putty\plink.exe -i C:\Users\tcbld1\.ssh\converted_for_putty_jenkins_id_rsa.ppk target-machine -l testuser touch plink
Java/tomcat-native ssh-agent Skipped registering Bounc圜astle, not running on a remote agent Started. If I enter the same command in cmd and enter the passphrase the command is actually executed.īuilding in workspace D:\jenkins\workspace\freestyletest Looking for ssh-agent implementation. This job is successful, but the command is not really executed, as if the passphrase is still necessary and just not entered. I'd assumed because ppk was the only valid format for me, that I would have to use putty's commands.īefore I had tried mysysgit's ssh command which doesn't seem to have the correct passphrase either. Then it always crashed if my credentials were not in putty's ppk format. I managed to "install" the native library by adding the path to the dll to the path and then restart Jenkins. mysysgit and putty's plink don't seem to profit from the agent.
When I have managed to get my credentials by ssh-agent I still don't know which ssh client command I am supposed to use then.
0 kommentar(er)
