That's my point. Why don't you try it the way I said: add the command on the ssh command line. That might be the way Jenkins tries to run your command and it might make a difference depending on your shell and it's configuration.
-- Sami Jason Losh <[email protected]> kirjoitti 9.2.2012 kello 0.14: > Hi Sami, > > Not exactly. I'm not using keys to establish the SSH connection. However, > under the Jenkins user account I am connecting as > > ssh <remoteaccount>@somehost.domain.com > > then after the password prompt I issue the command in the shell and it works. > In the SSH configuration in Jenkins I have it setup to use password > authentication which I provided. And when I click the "Test Configuration" > button I get a success result. > > Cheers, -Jason > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Sami Tikka > Sent: Tuesday, February 07, 2012 5:47 PM > To: [email protected] > Subject: Re: Problem with SSH publisher plug-in > > Dd you try to run the command from the Jenkins server as the Jenkins user > like this: > > ssh HOST "command_that_should_work" > > -- Sami > > [email protected] kirjoitti 7.2.2012 kello 21.44: > >> Hello, >> >> I am having difficulty running the exec command in the SSH publisher >> plug-in. I am able to successfully copy the source files of the build >> in the transfer set but the exec command fails. Here is the snippet >> from the log. >> >> SSH: Connecting from host [foo] >> SSH: Connecting with configuration [bar] ... >> SSH: EXEC: STDOUT/STDERR from command [test] ... >> SSH: Disconnecting configuration [bar] ... >> ERROR: Exception when publishing, exception message [Failed to connect >> exec channel. Message [session is down]] >> >> I can run the same command verbatim as what I have in the exec command >> field successfully using SSH outside of Jenkins. >> >> Has anyone else hit this? >> >> Thanks, -Jason > >
