Re: Host key verification failed

2022-12-05 Thread Edward Rolison 
I had this issue, and found the workaround was to run 'ssh-keyscan' and add
_all_ the keys to the '.ssh/known_hosts' file.



On Mon, 5 Dec 2022 at 12:45, 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Montag, dem 05.12.2022 um 18:03 +0530 schrieb Ram R:
>
> you need to check in the ssh plugin username and password
>
>
> Why? The error message clearly says "*HOST* key verification failed".
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/1607c084d2525dbc1a0b9ff37ada836923294c11.camel%40opentext.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1607c084d2525dbc1a0b9ff37ada836923294c11.camel%40opentext.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAJLp5qhe6bqLtEgkdexfXF9hy5vZ-QXcQ2PsXvQ8onKLsCVLtQ%40mail.gmail.com.

Re: Host key verification failed

2022-12-05 Thread 'Dirk Heinrichs' via Jenkins Users 
Am Montag, dem 05.12.2022 um 18:03 +0530 schrieb Ram R:

you need to check in the ssh plugin username and password

Why? The error message clearly says "HOST key verification failed".

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com<mailto:dhein...@opentext.com>
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/1607c084d2525dbc1a0b9ff37ada836923294c11.camel%40opentext.com.

Re: Host key verification failed

2022-12-05 Thread 'Dirk Heinrichs' via Jenkins Users 
Am Montag, dem 05.12.2022 um 17:55 +0530 schrieb pooja pooja:

While executing my job am getting below error can anyone help me on this issue?

No screenshots, please. Copy/paste is far anyway.

The problem seems to be in the script that is called. It seems to try to make 
an SSH connection to a remote host of which the key has not been accepted, yet 
(on the host that is running the job/stage).

HTH,

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/88b30b5819a0c450769e6866a2830ed2d9f14ac7.camel%40opentext.com.

Re: Host key verification failed

2022-12-05 Thread Ram R 
 I think you need to check in the ssh plugin username and password in
jenkins, there should be a connection issue.

Ramkrishna
9652540292



On Mon, Dec 5, 2022 at 5:55 PM pooja pooja  wrote:

> Hi all,
> While executing my job am getting below error can anyone help me on this
> issue?
>
> --
> 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/CANJUvtzQjRury4Ywu3AUwHV3L9a0a78niHcRV0OoV_wa6YBAQA%40mail.gmail.com
> 
> .
>

-- 
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/CABNk%2BKd1RKHgnNuNPtbEGYwm5bMV78tADaGS8Pb0ouqRJzwFpw%40mail.gmail.com.

Re: Host Key Verification Failed error

2015-05-20 Thread Paul Kilgo 
You can take a look at ssh-keyscan help build known_hosts databases
(maybe you are using that). The man page even says it can collect
1000s of host keys in tens of seconds.

Our Jenkins instance happens to be managed by Puppet which can do ssh
host key propagation for you, but it seems overkill if you aren't
already using it.

On Wed, May 20, 2015 at 5:03 PM, VFloyd vanettafl...@gmail.com wrote:
 Afternoon -
 How do you guys handle the Host Key Verification Failed msgs when
 deploying to new servers.

 I have 9 new build/deploy servers - one job can run on any of those deploy
 servers to move code to 12 servers in an environment.

 ssh'ing from each of the 9 new servers to each of the 12 servers for one job
 is not a problem and has already been done.  But ssh'ing from each of the 9
 servers to 1000's of other servers could become a problem (more so if
 someone decides to rebuild a random server or two).

 Any advise is appreciated.

 Vanetta


 --
 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/bed0b7b2-4d7e-48e7-b47c-cd29ecded3df%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/CAHNqWNPxC4tyJEZZopVwB0MudUs_%3DLPqkVs4FhnDenOGSrBycw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Host Key Verification Failed error

2015-05-20 Thread VFloyd 
Afternoon - 
How do you guys handle the Host Key Verification Failed msgs when 
deploying to new servers.  

I have 9 new build/deploy servers - one job can run on any of those deploy 
servers to move code to 12 servers in an environment.  

ssh'ing from each of the 9 new servers to each of the 12 servers for one 
job is not a problem and has already been done.  But ssh'ing from each of 
the 9 servers to 1000's of other servers could become a problem (more so if 
someone decides to rebuild a random server or two).

Any advise is appreciated.

Vanetta


-- 
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/bed0b7b2-4d7e-48e7-b47c-cd29ecded3df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Master [Execute Shell] Host Key Verification Failed

2014-03-18 Thread Jay Vyas 
I guess the answer to this is that : If SSH isnt set up properly on the 
machine your trying to SSH into, then the jenkins commands will fail.  

To test things : 

## become the jenkins user:
su jenkins -s /bin/bash

## Now try to ssh into the machine , mimicking the method you configured 
for the slave:
ssh root@my_slave

If this fails, then you know that the problem isn't necssarily in jenkins, 
but either 

1) sshd configuration on slave OR
2) ssh configuration on the master

In this case i think the solutoin was simply that we had to fiddle to allow 
password based auth on the slave (etc/ssh/sshd_config) , as well as on the 
master client (/etc/ssh/ssh_config).

On Monday, March 17, 2014 7:37:46 PM UTC-4, Jonathan Cope wrote:

 Hello,

 I'm new to Jenkins have some issue getting my jenkins master to connect to 
 my slave via SSH.

 My setup:

 1.  AWS EC2 instances ( 2 ) - m1.medium
 2.  Fedora-x86_64-20-20131211.1-sda  - AMI
 3.  Jenkins ver. 1.555
 4.  Passwordless Authentication from master to slave

 When I input the credentials
 user:jenkins
 credentials:  master ~/.ssh   OR  direct ssh key input

 It fails, with the log producing:

 [03/17/14 23:08:24] [SSH] Opening SSH connection to 
 ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
 http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/.
 [03/17/14 23:08:24] [SSH] Authentication failed.
 hudson.AbortException: Authentication failed.
   at 
 hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143)
   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648)
   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)
 [03/17/14 23:08:24] [SSH] Connection closed.
 [03/17/14 23:08:24] Launch failed - cleaning up connection




 I've been trying to diagnose the problem by running a simple job that passes 
 to the command line:


 ssh -Tv $usern...@ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
 http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/

 or

 ssh -Tv $username@PRIVATE-IP


 where username= root, jenkins, fedora, or no username


 This method consistently produces:


 Started by timer
 Building on master in workspace /var/lib/jenkins/jobs/test_jenkins/workspace
 [workspace] $ /bin/sh -xe /tmp/hudson5026502830242434855.sh
 + ssh -Tv slave ls  ### or username@slave
 OpenSSH_6.4, OpenSSL 1.0.1e-fips 11 Feb 2013
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: /etc/ssh/ssh_config line 51: Applying options for *
 debug1: Connecting to slave [##PRIVATE-IP##] port 22.
 debug1: Connection established.
 debug1: identity file /var/lib/jenkins/.ssh/id_rsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_rsa-cert type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_dsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_dsa-cert type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa-cert type -1
 debug1: Enabling compatibility mode for protocol 2.0
 debug1: Local version string SSH-2.0-OpenSSH_6.4
 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.3
 debug1: match: OpenSSH_6.3 pat OpenSSH*
 debug1: SSH2_MSG_KEXINIT sent
 debug1: SSH2_MSG_KEXINIT received
 debug1: kex: server-client aes128-ctr hmac-m...@openssh.com javascript: 
 none
 debug1: kex: client-server aes128-ctr hmac-m...@openssh.com javascript: 
 none
 debug1: sending SSH2_MSG_KEX_ECDH_INIT
 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
 debug1: Server host key: RSA  # key valuedebug1: read_passphrase: can't open 
 /dev/tty: No such device or address
 Host key verification failed.
 Build step 'Execute shell' marked build as failure
 Finished: FAILURE


 Hours of googling have produced myriad posts about this but I haven't found a 
 single working solution.




-- 
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.
For more options, visit https://groups.google.com/d/optout.

Jenkins Master [Execute Shell] Host Key Verification Failed

2014-03-17 Thread Jonathan Cope 
Hello,

I'm new to Jenkins have some issue getting my jenkins master to connect to 
my slave via SSH.

My setup:

1.  AWS EC2 instances ( 2 ) - m1.medium
2.  Fedora-x86_64-20-20131211.1-sda  - AMI
3.  Jenkins ver. 1.555
4.  Passwordless Authentication from master to slave

When I input the credentials
user:jenkins
credentials:  master ~/.ssh   OR  direct ssh key input

It fails, with the log producing:

[03/17/14 23:08:24] [SSH] Opening SSH connection to 
ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/.
[03/17/14 23:08:24] [SSH] Authentication failed.
hudson.AbortException: Authentication failed.
at 
hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
[03/17/14 23:08:24] [SSH] Connection closed.
[03/17/14 23:08:24] Launch failed - cleaning up connection




I've been trying to diagnose the problem by running a simple job that passes to 
the command line:


ssh -Tv $usern...@ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/

or

ssh -Tv $username@PRIVATE-IP


where username= root, jenkins, fedora, or no username


This method consistently produces:


Started by timer
Building on master in workspace /var/lib/jenkins/jobs/test_jenkins/workspace
[workspace] $ /bin/sh -xe /tmp/hudson5026502830242434855.sh
+ ssh -Tv slave ls  ### or username@slave
OpenSSH_6.4, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 51: Applying options for *
debug1: Connecting to slave [##PRIVATE-IP##] port 22.
debug1: Connection established.
debug1: identity file /var/lib/jenkins/.ssh/id_rsa type -1
debug1: identity file /var/lib/jenkins/.ssh/id_rsa-cert type -1
debug1: identity file /var/lib/jenkins/.ssh/id_dsa type -1
debug1: identity file /var/lib/jenkins/.ssh/id_dsa-cert type -1
debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa type -1
debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.3
debug1: match: OpenSSH_6.3 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5-...@openssh.com none
debug1: kex: client-server aes128-ctr hmac-md5-...@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA  # key valuedebug1: read_passphrase: can't open 
/dev/tty: No such device or address
Host key verification failed.
Build step 'Execute shell' marked build as failure
Finished: FAILURE


Hours of googling have produced myriad posts about this but I haven't found a 
single working solution.


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Master [Execute Shell] Host Key Verification Failed

2014-03-17 Thread Richard Bywater 
Given that you get the same on the command-line, it definitely looks like
your id_rsa key (or similar) has a passphrase attached.

Try doing a ssh-keygen -y. If you get prompted for a passphrase then I'd
say its definitely got a key attached.

Richard.


On Tue, Mar 18, 2014 at 12:37 PM, Jonathan Cope jcope.red...@gmail.comwrote:

 Hello,

 I'm new to Jenkins have some issue getting my jenkins master to connect to
 my slave via SSH.

 My setup:

 1.  AWS EC2 instances ( 2 ) - m1.medium
 2.  Fedora-x86_64-20-20131211.1-sda  - AMI
 3.  Jenkins ver. 1.555
 4.  Passwordless Authentication from master to slave

 When I input the credentials
 user:jenkins
 credentials:  master ~/.ssh   OR  direct ssh key input

 It fails, with the log producing:

 [03/17/14 23:08:24] [SSH] Opening SSH connection to 
 ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
 http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/.
 [03/17/14 23:08:24] [SSH] Authentication failed.
 hudson.AbortException: Authentication failed.
   at 
 hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143)
   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648)
   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)
 [03/17/14 23:08:24] [SSH] Connection closed.
 [03/17/14 23:08:24] Launch failed - cleaning up connection




 I've been trying to diagnose the problem by running a simple job that passes 
 to the command line:


 ssh -Tv $usern...@ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 
 http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/

 or

 ssh -Tv $username@PRIVATE-IP


 where username= root, jenkins, fedora, or no username


 This method consistently produces:


 Started by timer
 Building on master in workspace /var/lib/jenkins/jobs/test_jenkins/workspace
 [workspace] $ /bin/sh -xe /tmp/hudson5026502830242434855.sh
 + ssh -Tv slave ls  ### or username@slave
 OpenSSH_6.4, OpenSSL 1.0.1e-fips 11 Feb 2013
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: /etc/ssh/ssh_config line 51: Applying options for *
 debug1: Connecting to slave [##PRIVATE-IP##] port 22.
 debug1: Connection established.
 debug1: identity file /var/lib/jenkins/.ssh/id_rsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_rsa-cert type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_dsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_dsa-cert type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa type -1
 debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa-cert type -1
 debug1: Enabling compatibility mode for protocol 2.0
 debug1: Local version string SSH-2.0-OpenSSH_6.4
 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.3
 debug1: match: OpenSSH_6.3 pat OpenSSH*
 debug1: SSH2_MSG_KEXINIT sent
 debug1: SSH2_MSG_KEXINIT received
 debug1: kex: server-client aes128-ctr hmac-md5-...@openssh.com none
 debug1: kex: client-server aes128-ctr hmac-md5-...@openssh.com none
 debug1: sending SSH2_MSG_KEX_ECDH_INIT
 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
 debug1: Server host key: RSA  # key valuedebug1: read_passphrase: can't open 
 /dev/tty: No such device or address
 Host key verification failed.
 Build step 'Execute shell' marked build as failure
 Finished: FAILURE


 Hours of googling have produced myriad posts about this but I haven't found a 
 single working solution.


  --
 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.
 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.
For more options, visit https://groups.google.com/d/optout.