Powershell Script not getting failed in Jenkins

Question

I have downloaded SSH-Sessions by Joakim Svendsen which uses SSH.NET and installed the PowerShell module in the Jenkins Windows server

In Jenkins, I have the following PowerShell script:

Import-Module SSH-Sessions

$lastExitCode = 0
$devApp1 = "10.0.0.1"
$devApp2 = "10.0.0.2"

Write-Output "Deployment started in $devApp1......"

New-SshSession -ComputerName $devApp1 -Username test -Password test@123
$return = Invoke-SshCommand -ComputerName $devApp1  -Command "cd /NFS_DATA/autodeploy_scripts && echo test@123 | ./autodeploy.sh"

$return | Get-Member

if ($lastExitCode -ne 0)
{
    Write-Output $lastExitCode
    exit 1;
}
else
{
    Write-Output $lastExitCode
    exit 0;
}

The shell script contains:

#!/bin/bash
file="/NFS_DATA/autodeploy_scripts/test.log"
if [ -f "$file" ]
then
        echo "$file found."
        exit 0;
else
        echo "$file not found."
        exit 1;
fi

The problem is that the Jenkins job doesn't get failed when the file is not found. The Jenkins output is:

> Deployment started in 10.0.0.1...... Successfully connected to
> 10.0.0.01
> 10.0.0.01 had an error:

Finished: SUCCESS

After some suggestions I wrote the following PowerShell script using Posh-SSH. I'm also getting an error for this one, though it's different.

#Import-Module SSH-Sessions
Import-Module Posh-SSH

# Setup static variables
$devApp1="10.0.0.1"
$devApp2="10.0.0.2"
$username = "test"
$password = "test@123"
$command = "cd /NFS_DATA/autodeploy_scripts && echo Hybris@123 | ./autodeploy.sh"

Write-Output "Deployment started in $devApp1..."

# Setup PSCredentials
$secPasswd   = ConvertTo-SecureString $password -AsPlainText -Force
$credentials = New-Object System.Management.Automation.PSCredential ($username, $secPasswd) 
echo $credentials

# Estalbish new SSH session automatically accepting new SSH keys
$session = New-SSHSession -Computername $devApp1 -Credential $credentials -Acceptkey:$true

# Invoke command to be run on/in the SSH session
$output = Invoke-SSHCommand -SSHSession $session -Command $command

Write-Output "Returned Output from the Command: "
Write-Output $output.Output
Write-Output "Last Exit Status: "
Write-Output $output.ExitStatus

Getting the error message as:

The same code works in my local laptop, but fails in the Jenkins server.

I think in Jenkins server, due to Windows security restrictions, will not store the $secpasswd that is retrieved from the PSCredential. This causes only the username to be supplied to POSH.

How can I either fix those issues? How should I hardcode the password?

My assumption would be that nothing is happening because you're not passing on that error code from the PowerShell environment to Jenkins. As it is the PowerShell script exists with 0 unless there is an error while importing/establishing the session or Invoking the command. You would need to evaluate and return the code from Invoke-SSHCommand. — Seth
– Seth, Commented Apr 28, 2017 at 7:34
I'm new to powershell.. How to evaluate the Invoke-SSHCommand output — user2439278
– user2439278, Commented Apr 28, 2017 at 7:39
That would depend on how it's implemented. Look into the documentation for those cmdlets or play around with it. A good start would be to save what's returned to a variable. So $return = Invoke-SSHCommand .... After that you could use Get-Member to get more information or just let it print to the screen and have a look. Mind you that something like $? might be insufficient as the cmdlet itself might actually work fine, though the commands within error. — Seth
– Seth, Commented Apr 28, 2017 at 7:51
I'm clueless how to use Get-Member to evaluate the InvokeSSHCommand — user2439278
– user2439278, Commented Apr 28, 2017 at 9:32
The link actually contains an example for that. Shouldn't be that hard and you could also use it on the variable. You should do this on an interactive PowerShell and not in the script. Figure out what the invoke returns and adjust your script afterwards. As an example the default Invoke-Command cmdlet. You could also try to run Invoke-SSHCommand -? or Get-Help -Full Invoke-SSHCommand or use -Examples to get more information about how the cmdlet is supposed to work. — Seth
– Seth, Commented Apr 28, 2017 at 9:46

Seth · Accepted Answer · 2017-05-05 17:08:11Z

3

As you've never stated where those commands are coming from, I'm going to assume you're using Posh-SSH. By looking at this article about it, the solution would probably be:

$dev_app1="10.00.00.01"
$dev_app2="10.00.00.02"

echo "Deployment started in $dev_app1......"
Import-Module SSH-Sessions
New-SshSession -ComputerName $dev_app1 -Username test -Password test@123
$result = Invoke-SshCommand -ComputerName $dev_app1  -Command "cd /NFS_DATA/autodeploy_scripts && echo test@123 | ./autodeploy.sh"

Write-Output "Returned Output from the Command: "
Write-Output $result.Output
Write-Output "Last Exit Status: "
Write-Output $result.ExitStatus

if($result.ExitStatus -ne 0){
    exit $result.ExitStatus;
}

The if could be left out, it's just there for demonstration purposes. After all the exit status would be 0 otherwise.

The correct way to use Get-Member to get information about $result (in case this does not work) would be: $result | Get-Member. That will output the general attributes of whatever kind of object $result is.

As it would appear you're running this. You would need to run the following to get the objects:

$result = $SshSessions."$dev_app1".RunCommand('cd /NFS_DATA/autodeploy_scripts && echo test@123 | ./autodeploy.sh')

You'd use this instead of the Invoke-SshCommand and would need to change $result.Output to $result.Result.

edited May 5, 2017 at 17:08

answered May 5, 2017 at 9:34

Seth

1,25316 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

user2439278 Over a year ago

I have used $result | Get-Member , it displays the general attribute. How to proceed further

Seth Over a year ago

Either read the documentation on what those attributes mean or think about it. An attribute named Output probably will contain the output of the command executed by Invoke-SshCommand. So with your example script I'd expect the attribute to contain a text saying ... not found. If it does have an attribute ExitStatus check whenever it's 0 or 1 and possibly force the error to check whenever it changes to 1. After that use that information to let the script indicate an error (possibly by exiting with a non zero exit code).

user2439278 Over a year ago

I have downloaded powershelladmin.com/w/images/6/60/SSH-Sessions.zip and installed powershell module in the Jenkins windows server

user2439278 Over a year ago

I used Posh-SSH module now and updated the question with the error message

user2439278 Over a year ago

$result = $SshSessions."$dev_app1".RunCommand('cd /NFS_DATA/autodeploy_scripts && echo test@123 | ./autodeploy.sh') and Write-Output $result.Result works fine. How to fetch the exit code

|

Collectives™ on Stack Overflow

Powershell Script not getting failed in Jenkins

1 Answer 1

7 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

7 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related