subject:"Re\: Pipeline\: Transfer files via SSH"

Re: Pipeline: Transfer files via SSH

2017-06-23 Thread Ryan Kuharske

I know this is an old thread but I thought I'd post how I was able to get 
the issue resolved.

The issue we were having is that the ID which Jenkins runs with doesn't 
have access to the directory we needed to publish our artifacts to.  In 
order to get around this, we needed to ssh back into the server Jenkins is 
running on with a different ID that does have access to this directory.

To get it working, we had to copy the public key generated for our Jenkins 
ID into the authorized_keys file in the .ssh directory for the other user 
we wanted to connect as.  When setting up our credentials in Jenkins then, 
we set the username as the ID we wanted to connect with and chose to pull 
the private key from the Jenkins master folder (~/.ssh).

After that we were able to successfully connect to the server with those 
credentials.  It's probably fairly basic but it could be easy to mix up 
that step.

Hopefully it helps someone!

On Thursday, June 2, 2016 at 9:10:16 AM UTC-5, Sverre Moe wrote:
>
> I need to transfer some files to a server. 
> Have followed the suggestion mention in 
> https://issues.jenkins-ci.org/browse/JENKINS-27963
> Tried sshagent with both scp and rsync. Neither works.
>
> I have created a Credential for this server in Jenkins.
>
> Using rsync
> sshagent(['repository']) {
> sh "rsync -av *.rpm 
> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
> Host key verification failed.
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
>
> Using scp
> sshagent(['repository']) {
> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Host key verification failed.
> lost connection
>
> Problem because of this:
> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
> established.
> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
> [MD5].
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
> known hosts.
>
> Fixing this first "manually" and continued.
>
> Using rsync
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
> Using scp
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> lost connection
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9f906f1b-4a8d-480c-8921-8809f4bd7a89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

2017-06-23 Thread Ryan Kuharske

I know this is a very old topic, however I thought I'd add to it in case 
the original author will still get updates and for anyone else running into 
issues who comes across this thread.

For myself, the issue was not having the public key (that was generated on 
the server you're trying to connect to), in the authorized_keys file.

I'll explain a bit further to provide context.  Our Jenkins ID didn't have 
access to publish artifacts out to the folder we needed to push them to 
after doing the build.  In order to get around it, we were trying to setup 
a pipeline script and use sshagent to ssh back into the same server Jenkins 
is running on but with a different user ID.

In order to accomplish this, I logged onto the Jenkins server and navigated 
to the .ssh directory for the user that had the proper folder access.  From 
that location, I generated a new keypair, created the "authorized_keys" 
file (directly within the .ssh folder) and then added the newly generated 
public key into it.  That was the piece we were missing that was preventing 
us from properly connecting.  After that, we created the credential in 
Jenkins with the private key.  From there, we were able to use that user in 
our ssh command and it connected and executed commands properly.

On Thursday, June 2, 2016 at 9:10:16 AM UTC-5, Sverre Moe wrote:
>
> I need to transfer some files to a server. 
> Have followed the suggestion mention in 
> https://issues.jenkins-ci.org/browse/JENKINS-27963
> Tried sshagent with both scp and rsync. Neither works.
>
> I have created a Credential for this server in Jenkins.
>
> Using rsync
> sshagent(['repository']) {
> sh "rsync -av *.rpm 
> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
> Host key verification failed.
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
>
> Using scp
> sshagent(['repository']) {
> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Host key verification failed.
> lost connection
>
> Problem because of this:
> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
> established.
> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
> [MD5].
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
> known hosts.
>
> Fixing this first "manually" and continued.
>
> Using rsync
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
> Using scp
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> lost connection
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/46b0e807-e7f0-4593-a63c-7f9802dbde43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

2016-06-14 Thread Sverre Moe

Got the following debug output.

Wonder if it could have something to do with:
key_parse_private2: missing begin marker
However, the private key file has header "-BEGIN RSA PRIVATE KEY-" 
and footer "-END RSA PRIVATE KEY-"

debug2: key: private.key ((nil)), explicit
debug1: Authentications that can continue: publickey,keyboard-interactive
debug3: start over, passed a different list publickey,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: private.key
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey: RSA 
00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 [MD5]
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,keyboard-interactive
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 1

tirsdag 14. juni 2016 09.47.08 UTC+2 skrev Thomas Zoratto følgende:
>
> Ok, then try to ssh manually with full verbose mode (-vvv)
>
> Le 14 juin 2016 à 08:54, Sverre Moe  a 
> écrit :
>
> The private key is actually not password protected. I chose empty password 
> when I generated the private key on the server.
>
> tirsdag 14. juni 2016 08.41.17 UTC+2 skrev Thomas Zoratto følgende:
>>
>> Your private keys seems to be protected by a passphrase. As you are not 
>> in an interactive shell there is no tty so it fails when trying to ask for 
>> passphrase. 
>>
>> Le 14 juin 2016 à 08:20, Sverre Moe  a écrit :
>>
>> It looks like it is trying the private key credentials from Jenkins, but 
>> fails. When it fails it tries the public key for the user, then finally 
>> trying password which it cannot get.
>>
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: Next authentication method: publickey
>> debug1: Offering RSA public key: build (company-server)
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: Offering RSA public key: /home/build/.ssh/id_rsa
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: Trying private key: /home/build/.ssh/id_dsa
>> debug1: Trying private key: /home/build/.ssh/id_ecdsa
>> debug1: Next authentication method: keyboard-interactive
>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: No more authentication methods to try.
>> Permission denied (publickey,keyboard-interactive).
>>
>>
>> I don't think the problem is with either Jenkins og Agent SSH Plugin as I am 
>> getting almost the same problem manually executing ssh with the private key.
>>
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: Next authentication method: publickey
>> debug1: Trying private key: private.key
>> debug1: read PEM private key done: type RSA
>> debug1: Authentications that can continue: publickey,keyboard-interactive
>> debug1: Next authentication method: keyboard-interactive
>> Password: 
>>
>>
>> mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende:
>>>
>>> Hi,
>>>
>>> Try to ssh in verbose mode and you'll know what's happening. 
>>>
>>> ssh -v ... 
>>>
>>> (The more v you put, the more verbose it will be)
>>>
>>> Le 13 juin 2016 à 15:21, Sverre Moe  a écrit :
>>>
>>> I have already added the host to ~/.ssh/known_hosts, so 
>>> using StrictHostKeyChecking=no is no longer necessary.
>>> What I am experiencing now is authentication problem. It does not use 
>>> the credentials with the ssh connection. Thus I receive Permission denied 
>>> (publickey,keyboard-interactive).
>>>
>>> My credentials contain the private key for the username I use in the ssh 
>>> command.
>>>
>>> Wonder if the problem lies not with sshagent, but elsewhere.
>>> I have tried the following command manually with the same private-key 
>>> stored in Jenkins for this user and it still asks for password.
>>> ssh -i private.key bu...@server.company.com
>>> Password: 
>>> Password: 
>>> Password: 
>>>

Re: Pipeline: Transfer files via SSH

2016-06-14 Thread Zoratto Thomas

Ok, then try to ssh manually with full verbose mode (-vvv)

> Le 14 juin 2016 à 08:54, Sverre Moe  a écrit :
> 
> The private key is actually not password protected. I chose empty password 
> when I generated the private key on the server.
> 
> tirsdag 14. juni 2016 08.41.17 UTC+2 skrev Thomas Zoratto følgende:
>> 
>> Your private keys seems to be protected by a passphrase. As you are not in 
>> an interactive shell there is no tty so it fails when trying to ask for 
>> passphrase. 
>> 
>>> Le 14 juin 2016 à 08:20, Sverre Moe  a écrit :
>>> 
>>> It looks like it is trying the private key credentials from Jenkins, but 
>>> fails. When it fails it tries the public key for the user, then finally 
>>> trying password which it cannot get.
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: Next authentication method: publickey
>>> debug1: Offering RSA public key: build (company-server)
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: Offering RSA public key: /home/build/.ssh/id_rsa
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: Trying private key: /home/build/.ssh/id_dsa
>>> debug1: Trying private key: /home/build/.ssh/id_ecdsa
>>> debug1: Next authentication method: keyboard-interactive
>>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: read_passphrase: can't open /dev/tty: No such device or address
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: No more authentication methods to try.
>>> Permission denied (publickey,keyboard-interactive).
>>> 
>>> I don't think the problem is with either Jenkins og Agent SSH Plugin as I 
>>> am getting almost the same problem manually executing ssh with the private 
>>> key.
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: Next authentication method: publickey
>>> debug1: Trying private key: private.key
>>> debug1: read PEM private key done: type RSA
>>> debug1: Authentications that can continue: publickey,keyboard-interactive
>>> debug1: Next authentication method: keyboard-interactive
>>> Password: 
>>> 
>>> mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende:
 
 Hi,
 
 Try to ssh in verbose mode and you'll know what's happening. 
 
 ssh -v ... 
 
 (The more v you put, the more verbose it will be)
 
> Le 13 juin 2016 à 15:21, Sverre Moe  a écrit :
> 
> I have already added the host to ~/.ssh/known_hosts, so using 
> StrictHostKeyChecking=no is no longer necessary.
> What I am experiencing now is authentication problem. It does not use the 
> credentials with the ssh connection. Thus I receive Permission denied 
> (publickey,keyboard-interactive).
> 
> My credentials contain the private key for the username I use in the ssh 
> command.
> 
> Wonder if the problem lies not with sshagent, but elsewhere.
> I have tried the following command manually with the same private-key 
> stored in Jenkins for this user and it still asks for password.
> ssh -i private.key bu...@server.company.com
> Password: 
> Password: 
> Password: 
> Permission denied (publickey,keyboard-interactive).
> 
> However still do sshagent supply the private key when executing ssh?
> 
> 
> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
>> 
>> Indeed in my case I had disabled host key checking. 
>> 
>> What works for me is:
>> 
>> sshagent(['some-id']) { 
>>  
>> sh """
>>  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
>> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
>> container already existing?' "
>>  
>> """
>> }
>> 
>> 2016-06-13 9:53 GMT+00:00 Sverre Moe :
>>> Am i missing something in my script content?
>>> sshagent(['repository']) {
>>> sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
>>> }
>>> 
>>> When executing ssh within sshagent I am getting
>>> Permission denied (publickey,keyboard-interactive).
>>> 
>>> The credential repository has the private key for the user build.
>>> 
>>> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
 
 I need to transfer some files to a server. 
 Have followed the suggestion mention in 
 https://issues.jenkins-ci.org/browse/JENKINS-27963
 Tried sshagent with both scp and rsync. Neither works.

Re: Pipeline: Transfer files via SSH

2016-06-14 Thread Sverre Moe

The private key is actually not password protected. I chose empty password 
when I generated the private key on the server.

tirsdag 14. juni 2016 08.41.17 UTC+2 skrev Thomas Zoratto følgende:
>
> Your private keys seems to be protected by a passphrase. As you are not in 
> an interactive shell there is no tty so it fails when trying to ask for 
> passphrase. 
>
> Le 14 juin 2016 à 08:20, Sverre Moe  a 
> écrit :
>
> It looks like it is trying the private key credentials from Jenkins, but 
> fails. When it fails it tries the public key for the user, then finally 
> trying password which it cannot get.
>
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: publickey
> debug1: Offering RSA public key: build (company-server)
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Offering RSA public key: /home/build/.ssh/id_rsa
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Trying private key: /home/build/.ssh/id_dsa
> debug1: Trying private key: /home/build/.ssh/id_ecdsa
> debug1: Next authentication method: keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
>
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
>
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
>
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: No more authentication methods to try.
> Permission denied (publickey,keyboard-interactive).
>
>
> I don't think the problem is with either Jenkins og Agent SSH Plugin as I am 
> getting almost the same problem manually executing ssh with the private key.
>
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: publickey
> debug1: Trying private key: private.key
> debug1: read PEM private key done: type RSA
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: keyboard-interactive
> Password: 
>
>
> mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende:
>>
>> Hi,
>>
>> Try to ssh in verbose mode and you'll know what's happening. 
>>
>> ssh -v ... 
>>
>> (The more v you put, the more verbose it will be)
>>
>> Le 13 juin 2016 à 15:21, Sverre Moe  a écrit :
>>
>> I have already added the host to ~/.ssh/known_hosts, so 
>> using StrictHostKeyChecking=no is no longer necessary.
>> What I am experiencing now is authentication problem. It does not use the 
>> credentials with the ssh connection. Thus I receive Permission denied 
>> (publickey,keyboard-interactive).
>>
>> My credentials contain the private key for the username I use in the ssh 
>> command.
>>
>> Wonder if the problem lies not with sshagent, but elsewhere.
>> I have tried the following command manually with the same private-key 
>> stored in Jenkins for this user and it still asks for password.
>> ssh -i private.key bu...@server.company.com
>> Password: 
>> Password: 
>> Password: 
>> Permission denied (publickey,keyboard-interactive).
>>
>> However still do sshagent supply the private key when executing ssh?
>>
>>
>> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
>>>
>>> Indeed in my case I had disabled host key checking. 
>>>
>>> What works for me is:
>>>
>>> sshagent(['some-id']) { 
>>>  
>>> sh """
>>>  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
>>> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
>>> container already existing?' "
>>>  
>>> """
>>> }
>>>
>>> 2016-06-13 9:53 GMT+00:00 Sverre Moe :
>>>
 Am i missing something in my script content?
 sshagent(['repository']) {
 sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
 }

 When executing ssh within sshagent I am getting
 Permission denied (publickey,keyboard-interactive).

 The credential repository has the private key for the user build.

 torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
>
> I need to transfer some files to a server. 
> Have followed the suggestion mention in 
> https://issues.jenkins-ci.org/browse/JENKINS-27963
> Tried sshagent with both scp and rsync. Neither works.
>
> I have created a Credential for this server in Jenkins.
>
> Using rsync
> sshagent(['repository']) {
> sh "rsync -av *.rpm ro...@server.company.com
> :/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
>

Re: Pipeline: Transfer files via SSH

2016-06-14 Thread Zoratto Thomas

Your private keys seems to be protected by a passphrase. As you are not in an 
interactive shell there is no tty so it fails when trying to ask for 
passphrase. 

> Le 14 juin 2016 à 08:20, Sverre Moe  a écrit :
> 
> It looks like it is trying the private key credentials from Jenkins, but 
> fails. When it fails it tries the public key for the user, then finally 
> trying password which it cannot get.
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: publickey
> debug1: Offering RSA public key: build (company-server)
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Offering RSA public key: /home/build/.ssh/id_rsa
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Trying private key: /home/build/.ssh/id_dsa
> debug1: Trying private key: /home/build/.ssh/id_ecdsa
> debug1: Next authentication method: keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: read_passphrase: can't open /dev/tty: No such device or address
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: No more authentication methods to try.
> Permission denied (publickey,keyboard-interactive).
> 
> I don't think the problem is with either Jenkins og Agent SSH Plugin as I am 
> getting almost the same problem manually executing ssh with the private key.
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: publickey
> debug1: Trying private key: private.key
> debug1: read PEM private key done: type RSA
> debug1: Authentications that can continue: publickey,keyboard-interactive
> debug1: Next authentication method: keyboard-interactive
> Password: 
> 
> mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende:
>> 
>> Hi,
>> 
>> Try to ssh in verbose mode and you'll know what's happening. 
>> 
>> ssh -v ... 
>> 
>> (The more v you put, the more verbose it will be)
>> 
>>> Le 13 juin 2016 à 15:21, Sverre Moe  a écrit :
>>> 
>>> I have already added the host to ~/.ssh/known_hosts, so using 
>>> StrictHostKeyChecking=no is no longer necessary.
>>> What I am experiencing now is authentication problem. It does not use the 
>>> credentials with the ssh connection. Thus I receive Permission denied 
>>> (publickey,keyboard-interactive).
>>> 
>>> My credentials contain the private key for the username I use in the ssh 
>>> command.
>>> 
>>> Wonder if the problem lies not with sshagent, but elsewhere.
>>> I have tried the following command manually with the same private-key 
>>> stored in Jenkins for this user and it still asks for password.
>>> ssh -i private.key bu...@server.company.com
>>> Password: 
>>> Password: 
>>> Password: 
>>> Permission denied (publickey,keyboard-interactive).
>>> 
>>> However still do sshagent supply the private key when executing ssh?
>>> 
>>> 
>>> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
 
 Indeed in my case I had disabled host key checking. 
 
 What works for me is:
 
 sshagent(['some-id']) { 
  
 sh """
  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
 create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
 container already existing?' "
  
 """
 }
 
 2016-06-13 9:53 GMT+00:00 Sverre Moe :
> Am i missing something in my script content?
> sshagent(['repository']) {
> sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
> }
> 
> When executing ssh within sshagent I am getting
> Permission denied (publickey,keyboard-interactive).
> 
> The credential repository has the private key for the user build.
> 
> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
>> 
>> I need to transfer some files to a server. 
>> Have followed the suggestion mention in 
>> https://issues.jenkins-ci.org/browse/JENKINS-27963
>> Tried sshagent with both scp and rsync. Neither works.
>> 
>> I have created a Credential for this server in Jenkins.
>> 
>> Using rsync
>> sshagent(['repository']) {
>> sh "rsync -av *.rpm 
>> ro...@server.company.com:/srv/www/htdocs/staging_rpms/"
>> }
>> 
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + rsync -av *.rpm

Re: Pipeline: Transfer files via SSH

2016-06-14 Thread Sverre Moe

It looks like it is trying the private key credentials from Jenkins, but 
fails. When it fails it tries the public key for the user, then finally 
trying password which it cannot get.

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: build (company-server)
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Offering RSA public key: /home/build/.ssh/id_rsa
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Trying private key: /home/build/.ssh/id_dsa
debug1: Trying private key: /home/build/.ssh/id_ecdsa
debug1: Next authentication method: keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: No such device or address

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: No such device or address

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: No such device or address

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,keyboard-interactive).


I don't think the problem is with either Jenkins og Agent SSH Plugin as I am 
getting almost the same problem manually executing ssh with the private key.

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: private.key
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
Password: 


mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende:
>
> Hi,
>
> Try to ssh in verbose mode and you'll know what's happening. 
>
> ssh -v ... 
>
> (The more v you put, the more verbose it will be)
>
> Le 13 juin 2016 à 15:21, Sverre Moe  a 
> écrit :
>
> I have already added the host to ~/.ssh/known_hosts, so 
> using StrictHostKeyChecking=no is no longer necessary.
> What I am experiencing now is authentication problem. It does not use the 
> credentials with the ssh connection. Thus I receive Permission denied 
> (publickey,keyboard-interactive).
>
> My credentials contain the private key for the username I use in the ssh 
> command.
>
> Wonder if the problem lies not with sshagent, but elsewhere.
> I have tried the following command manually with the same private-key 
> stored in Jenkins for this user and it still asks for password.
> ssh -i private.key bu...@server.company.com
> Password: 
> Password: 
> Password: 
> Permission denied (publickey,keyboard-interactive).
>
> However still do sshagent supply the private key when executing ssh?
>
>
> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
>>
>> Indeed in my case I had disabled host key checking. 
>>
>> What works for me is:
>>
>> sshagent(['some-id']) { 
>>  
>> sh """
>>  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
>> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
>> container already existing?' "
>>  
>> """
>> }
>>
>> 2016-06-13 9:53 GMT+00:00 Sverre Moe :
>>
>>> Am i missing something in my script content?
>>> sshagent(['repository']) {
>>> sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
>>> }
>>>
>>> When executing ssh within sshagent I am getting
>>> Permission denied (publickey,keyboard-interactive).
>>>
>>> The credential repository has the private key for the user build.
>>>
>>> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:

 I need to transfer some files to a server. 
 Have followed the suggestion mention in 
 https://issues.jenkins-ci.org/browse/JENKINS-27963
 Tried sshagent with both scp and rsync. Neither works.

 I have created a Credential for this server in Jenkins.

 Using rsync
 sshagent(['repository']) {
 sh "rsync -av *.rpm ro...@server.company.com 
 :/srv/www/htdocs/staging_rpms/"
 }

 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking for ssh-agent implementation...
 [ssh-agent]   Java/JNR ssh-agent
 [ssh-agent] Started.
 [Pipeline] {
 [Pipeline] sh
 [master] Running shell script
 + rsync -av *.rpm ro...@server.company.com 
 :/srv/www/htdocs/staging_rpms
 Host key verification failed.
 rsync: connection unexpectedly closed (0 bytes received so far) [sender]
 rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
 [sender=3.0.4]


 Using scp
 sshagent(['repository']) {
 sh "scp *.rpm ro...@server.company.com 
 :/srv/www/htdocs/staging_rpms/"
 }

 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking

Re: Pipeline: Transfer files via SSH

2016-06-13 Thread Zoratto Thomas

Hi,

Try to ssh in verbose mode and you'll know what's happening. 

ssh -v ... 

(The more v you put, the more verbose it will be)

> Le 13 juin 2016 à 15:21, Sverre Moe  a écrit :
> 
> I have already added the host to ~/.ssh/known_hosts, so using 
> StrictHostKeyChecking=no is no longer necessary.
> What I am experiencing now is authentication problem. It does not use the 
> credentials with the ssh connection. Thus I receive Permission denied 
> (publickey,keyboard-interactive).
> 
> My credentials contain the private key for the username I use in the ssh 
> command.
> 
> Wonder if the problem lies not with sshagent, but elsewhere.
> I have tried the following command manually with the same private-key stored 
> in Jenkins for this user and it still asks for password.
> ssh -i private.key bu...@server.company.com
> Password: 
> Password: 
> Password: 
> Permission denied (publickey,keyboard-interactive).
> 
> However still do sshagent supply the private key when executing ssh?
> 
> 
> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
>> 
>> Indeed in my case I had disabled host key checking. 
>> 
>> What works for me is:
>> 
>> sshagent(['some-id']) { 
>>  
>> sh """
>>  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
>> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
>> container already existing?' "
>>  
>> """
>> }
>> 
>> 2016-06-13 9:53 GMT+00:00 Sverre Moe :
>>> Am i missing something in my script content?
>>> sshagent(['repository']) {
>>> sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
>>> }
>>> 
>>> When executing ssh within sshagent I am getting
>>> Permission denied (publickey,keyboard-interactive).
>>> 
>>> The credential repository has the private key for the user build.
>>> 
>>> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
 
 I need to transfer some files to a server. 
 Have followed the suggestion mention in 
 https://issues.jenkins-ci.org/browse/JENKINS-27963
 Tried sshagent with both scp and rsync. Neither works.
 
 I have created a Credential for this server in Jenkins.
 
 Using rsync
 sshagent(['repository']) {
 sh "rsync -av *.rpm 
 r...@server.company.com:/srv/www/htdocs/staging_rpms/"
 }
 
 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking for ssh-agent implementation...
 [ssh-agent]   Java/JNR ssh-agent
 [ssh-agent] Started.
 [Pipeline] {
 [Pipeline] sh
 [master] Running shell script
 + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
 Host key verification failed.
 rsync: connection unexpectedly closed (0 bytes received so far) [sender]
 rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
 [sender=3.0.4]
 
 
 Using scp
 sshagent(['repository']) {
 sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
 }
 
 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking for ssh-agent implementation...
 [ssh-agent]   Java/JNR ssh-agent
 [ssh-agent] Started.
 [Pipeline] {
 [Pipeline] sh
 [master] Running shell script
 + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
 Host key verification failed.
 lost connection
 
 Problem because of this:
 The authenticity of host 'server.company.com (192.24.17.73)' can't be 
 established.
 ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
 [MD5].
 Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
 known hosts.
 
 Fixing this first "manually" and continued.
 
 Using rsync
 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking for ssh-agent implementation...
 [ssh-agent]   Java/JNR ssh-agent
 [ssh-agent] Started.
 [Pipeline] {
 [Pipeline] sh
 [master] Running shell script
 + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
 Permission denied (publickey,keyboard-interactive).
 rsync: connection unexpectedly closed (0 bytes received so far) [sender]
 rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
 [sender=3.0.4]
 
 Using scp
 [ssh-agent] Using credentials build (repohost)
 [ssh-agent] Looking for ssh-agent implementation...
 [ssh-agent]   Java/JNR ssh-agent
 [ssh-agent] Started.
 [Pipeline] {
 [Pipeline] sh
 [master] Running shell script
 + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
 Permission denied (publickey,keyboard-interactive).
 lost connection
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Users" group.
>>> To

Re: Pipeline: Transfer files via SSH

2016-06-13 Thread Sverre Moe

I have already added the host to ~/.ssh/known_hosts, so 
using StrictHostKeyChecking=no is no longer necessary.
What I am experiencing now is authentication problem. It does not use the 
credentials with the ssh connection. Thus I receive Permission denied 
(publickey,keyboard-interactive).

My credentials contain the private key for the username I use in the ssh 
command.

Wonder if the problem lies not with sshagent, but elsewhere.
I have tried the following command manually with the same private-key 
stored in Jenkins for this user and it still asks for password.
ssh -i private.key bu...@server.company.com
Password: 
Password: 
Password: 
Permission denied (publickey,keyboard-interactive).

However still do sshagent supply the private key when executing ssh?


mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende:
>
> Indeed in my case I had disabled host key checking. 
>
> What works for me is:
>
> sshagent(['some-id']) { 
>  
> sh """
>  ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker 
> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data 
> container already existing?' "
>  
> """
> }
>
> 2016-06-13 9:53 GMT+00:00 Sverre Moe :
>
>> Am i missing something in my script content?
>> sshagent(['repository']) {
>> sh 'ssh -Xf bu...@repo.company.com  ls -l /home/build/ '
>> }
>>
>> When executing ssh within sshagent I am getting
>> Permission denied (publickey,keyboard-interactive).
>>
>> The credential repository has the private key for the user build.
>>
>> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
>>>
>>> I need to transfer some files to a server. 
>>> Have followed the suggestion mention in 
>>> https://issues.jenkins-ci.org/browse/JENKINS-27963
>>> Tried sshagent with both scp and rsync. Neither works.
>>>
>>> I have created a Credential for this server in Jenkins.
>>>
>>> Using rsync
>>> sshagent(['repository']) {
>>> sh "rsync -av *.rpm 
>>> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>>> }
>>>
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
>>> Host key verification failed.
>>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>>> [sender=3.0.4]
>>>
>>>
>>> Using scp
>>> sshagent(['repository']) {
>>> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>>> }
>>>
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Host key verification failed.
>>> lost connection
>>>
>>> Problem because of this:
>>> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
>>> established.
>>> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
>>> [MD5].
>>> Are you sure you want to continue connecting (yes/no)? yes
>>> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
>>> known hosts.
>>>
>>> Fixing this first "manually" and continued.
>>>
>>> Using rsync
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Permission denied (publickey,keyboard-interactive).
>>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>>> [sender=3.0.4]
>>>
>>> Using scp
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Permission denied (publickey,keyboard-interactive).
>>> lost connection
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/db0ba327-53d3-46f4-a09d-feeb3d539104%40googlegroups.com
>>  
>>

Re: Pipeline: Transfer files via SSH

2016-06-13 Thread Baptiste Mathus

Indeed in my case I had disabled host key checking.

What works for me is:

sshagent(['some-id']) {

sh """
 ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker
create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo 'data
container already existing?' "
 
"""
}

2016-06-13 9:53 GMT+00:00 Sverre Moe :

> Am i missing something in my script content?
> sshagent(['repository']) {
> sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
> }
>
> When executing ssh within sshagent I am getting
> Permission denied (publickey,keyboard-interactive).
>
> The credential repository has the private key for the user build.
>
> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
>>
>> I need to transfer some files to a server.
>> Have followed the suggestion mention in
>> https://issues.jenkins-ci.org/browse/JENKINS-27963
>> Tried sshagent with both scp and rsync. Neither works.
>>
>> I have created a Credential for this server in Jenkins.
>>
>> Using rsync
>> sshagent(['repository']) {
>> sh "rsync -av *.rpm r...@server.company.com:
>> /srv/www/htdocs/staging_rpms/"
>> }
>>
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
>> Host key verification failed.
>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(641)
>> [sender=3.0.4]
>>
>>
>> Using scp
>> sshagent(['repository']) {
>> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>> }
>>
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Host key verification failed.
>> lost connection
>>
>> Problem because of this:
>> The authenticity of host 'server.company.com (192.24.17.73)' can't be
>> established.
>> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18
>> [MD5].
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added 'server.company.com' (ECDSA) to the list of
>> known hosts.
>>
>> Fixing this first "manually" and continued.
>>
>> Using rsync
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Permission denied (publickey,keyboard-interactive).
>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(641)
>> [sender=3.0.4]
>>
>> Using scp
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Permission denied (publickey,keyboard-interactive).
>> lost connection
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/db0ba327-53d3-46f4-a09d-feeb3d539104%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7J0zP%3Dr_0MzbEgagz5inhbvbDEvKkb71%3DyUTrQ7%2B1cAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

2016-06-13 Thread Sverre Moe

Am i missing something in my script content?
sshagent(['repository']) {
sh 'ssh -Xf bu...@repo.company.com ls -l /home/build/ '
}

When executing ssh within sshagent I am getting
Permission denied (publickey,keyboard-interactive).

The credential repository has the private key for the user build.

torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende:
>
> I need to transfer some files to a server. 
> Have followed the suggestion mention in 
> https://issues.jenkins-ci.org/browse/JENKINS-27963
> Tried sshagent with both scp and rsync. Neither works.
>
> I have created a Credential for this server in Jenkins.
>
> Using rsync
> sshagent(['repository']) {
> sh "rsync -av *.rpm 
> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
> Host key verification failed.
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
>
> Using scp
> sshagent(['repository']) {
> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Host key verification failed.
> lost connection
>
> Problem because of this:
> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
> established.
> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
> [MD5].
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
> known hosts.
>
> Fixing this first "manually" and continued.
>
> Using rsync
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
> [sender=3.0.4]
>
> Using scp
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> lost connection
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/db0ba327-53d3-46f4-a09d-feeb3d539104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

2016-06-06 Thread Sverre Moe

I could perhaps circumvent this problem by adding the build users public 
key from each slave node to authorized_keys on the server. Then I would not 
need to use the credentials on Jenkins. However I see that only as a 
fallback option. Best approach would be to use authentication from Jenkins 
Crendentials.

mandag 6. juni 2016 09.06.59 UTC+2 skrev Sverre Moe følgende:
>
> Using the following with ssh I can disable host key verification
> ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no 
> r...@server.company.com
> also 
> scp  -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no *.rpm 
> r...@server.company.com:/tmp
>
> Warning: Permanently added 'server.company.com,145.235.17.27' (ECDSA) to 
> the list of known hosts
> But it does not actually add it to know_hosts, which is actually a good 
> thing. Ignoring host key verification does have consequences.
>
>
> However my next problem still remains. Getting Permission denied 
> (publickey,keyboard-interactive)
> How does it use the credentials private key from Jenkins in the 
> ssh/scp/rsync command?
>
>
> lørdag 4. juni 2016 15.15.48 UTC+2 skrev Baptiste Mathus følgende:
>>
>> Did you try passing the host key checking ssh parameter to "no"?
>> Le 2 juin 2016 4:10 PM, "Sverre Moe"  a écrit :
>>
>>> I need to transfer some files to a server. 
>>> Have followed the suggestion mention in 
>>> https://issues.jenkins-ci.org/browse/JENKINS-27963
>>> Tried sshagent with both scp and rsync. Neither works.
>>>
>>> I have created a Credential for this server in Jenkins.
>>>
>>> Using rsync
>>> sshagent(['repository']) {
>>> sh "rsync -av *.rpm 
>>> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>>> }
>>>
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
>>> Host key verification failed.
>>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>>> [sender=3.0.4]
>>>
>>>
>>> Using scp
>>> sshagent(['repository']) {
>>> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>>> }
>>>
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Host key verification failed.
>>> lost connection
>>>
>>> Problem because of this:
>>> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
>>> established.
>>> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
>>> [MD5].
>>> Are you sure you want to continue connecting (yes/no)? yes
>>> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
>>> known hosts.
>>>
>>> Fixing this first "manually" and continued.
>>>
>>> Using rsync
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Permission denied (publickey,keyboard-interactive).
>>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>>> [sender=3.0.4]
>>>
>>> Using scp
>>> [ssh-agent] Using credentials build (repohost)
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Java/JNR ssh-agent
>>> [ssh-agent] Started.
>>> [Pipeline] {
>>> [Pipeline] sh
>>> [master] Running shell script
>>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>>> Permission denied (publickey,keyboard-interactive).
>>> lost connection
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/fb3f547a-32ad-49b0-a012-9dfa69f91a35%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.

Re: Pipeline: Transfer files via SSH

2016-06-06 Thread Sverre Moe

Using the following with ssh I can disable host key verification
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@server.
company.com
also 
scp  -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no *.rpm 
r...@server.company.com:/tmp

Warning: Permanently added 'server.company.com,145.235.17.27' (ECDSA) to 
the list of known hosts
But it does not actually add it to know_hosts, which is actually a good 
thing. Ignoring host key verification does have consequences.


However my next problem still remains. Getting Permission denied 
(publickey,keyboard-interactive)
How does it use the credentials private key from Jenkins in the 
ssh/scp/rsync command?


lørdag 4. juni 2016 15.15.48 UTC+2 skrev Baptiste Mathus følgende:
>
> Did you try passing the host key checking ssh parameter to "no"?
> Le 2 juin 2016 4:10 PM, "Sverre Moe"  a 
> écrit :
>
>> I need to transfer some files to a server. 
>> Have followed the suggestion mention in 
>> https://issues.jenkins-ci.org/browse/JENKINS-27963
>> Tried sshagent with both scp and rsync. Neither works.
>>
>> I have created a Credential for this server in Jenkins.
>>
>> Using rsync
>> sshagent(['repository']) {
>> sh "rsync -av *.rpm 
>> r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>> }
>>
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
>> Host key verification failed.
>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>> [sender=3.0.4]
>>
>>
>> Using scp
>> sshagent(['repository']) {
>> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
>> }
>>
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Host key verification failed.
>> lost connection
>>
>> Problem because of this:
>> The authenticity of host 'server.company.com (192.24.17.73)' can't be 
>> established.
>> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 
>> [MD5].
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added 'server.company.com' (ECDSA) to the list of 
>> known hosts.
>>
>> Fixing this first "manually" and continued.
>>
>> Using rsync
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Permission denied (publickey,keyboard-interactive).
>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(641) 
>> [sender=3.0.4]
>>
>> Using scp
>> [ssh-agent] Using credentials build (repohost)
>> [ssh-agent] Looking for ssh-agent implementation...
>> [ssh-agent]   Java/JNR ssh-agent
>> [ssh-agent] Started.
>> [Pipeline] {
>> [Pipeline] sh
>> [master] Running shell script
>> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
>> Permission denied (publickey,keyboard-interactive).
>> lost connection
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/fb3f547a-32ad-49b0-a012-9dfa69f91a35%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f17ee7c0-5851-430b-a1a9-2de122b75aa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

2016-06-04 Thread Baptiste Mathus

Did you try passing the host key checking ssh parameter to "no"?
Le 2 juin 2016 4:10 PM, "Sverre Moe"  a écrit :

> I need to transfer some files to a server.
> Have followed the suggestion mention in
> https://issues.jenkins-ci.org/browse/JENKINS-27963
> Tried sshagent with both scp and rsync. Neither works.
>
> I have created a Credential for this server in Jenkins.
>
> Using rsync
> sshagent(['repository']) {
> sh "rsync -av *.rpm r...@server.company.com:
> /srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms
> Host key verification failed.
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641)
> [sender=3.0.4]
>
>
> Using scp
> sshagent(['repository']) {
> sh "scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/"
> }
>
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Host key verification failed.
> lost connection
>
> Problem because of this:
> The authenticity of host 'server.company.com (192.24.17.73)' can't be
> established.
> ECDSA key fingerprint is 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18
> [MD5].
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'server.company.com' (ECDSA) to the list of
> known hosts.
>
> Fixing this first "manually" and continued.
>
> Using rsync
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + rsync -av *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(641)
> [sender=3.0.4]
>
> Using scp
> [ssh-agent] Using credentials build (repohost)
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Started.
> [Pipeline] {
> [Pipeline] sh
> [master] Running shell script
> + scp *.rpm r...@server.company.com:/srv/www/htdocs/staging_rpms/
> Permission denied (publickey,keyboard-interactive).
> lost connection
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/fb3f547a-32ad-49b0-a012-9dfa69f91a35%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6exadWL9_w3kqgdhwfxh5qNW5aU8SxTmkHGH42SnfwTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

Re: Pipeline: Transfer files via SSH

14 matches

Site Navigation

Mail list logo

Footer information