How can I get powershell to return the correct exit code when called with the -File argument?

Question

Powershell is returning a 0 exit code, when an error has occurred, if called with the -File argument. Which means my build is green when it shouldn't be :(

For example:

(in wtf.ps1)

$ErrorActionPreference = "Stop";   
$null.split()

(cmd)

powershell -file c:\wtf.ps1  
You cannot call a method on a null-valued expression.
At C:\wtf.ps1:3 char:12
+ $null.split <<<< ()
    + CategoryInfo          : InvalidOperation: (split:String) [], ParentConta
   insErrorRecordException
    + FullyQualifiedErrorId : InvokeMethodOnNull


echo %errorlevel%  
0

powershell c:\wtf.ps1  
You cannot call a method on a null-valued expression.
At C:\wtf.ps1:3 char:12
+ $null.split <<<< ()
    + CategoryInfo          : InvalidOperation: (split:String) [], ParentConta
   insErrorRecordException
    + FullyQualifiedErrorId : InvokeMethodOnNull


echo %errorlevel%  
1

Any ideas?

(I've tried pretty much every idea from the first 2 pages of this: https://www.google.co.uk/search?q=powershell+file+argument+exit+code already)

Shay Levy · Accepted Answer · 2012-05-16 15:19:16Z

13

In the script, use the exit keyword with a number of your choice:

exit 34

Here's the script I used to test this:

## D:\Scripts\Temp\exit.ps1 ##
try{
    $null.split()
}
catch
{
    exit 34
}

exit 2
#############################

# launch powershell from cmd 
C:\> powershell -noprofile -file D:\Scripts\Temp\exit.ps1
C:\>echo %errorlevel%
34

edited May 16, 2012 at 15:19

answered May 16, 2012 at 14:35

Shay Levy

128k34 gold badges193 silver badges210 bronze badges

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

2 Comments

grahamrhay Over a year ago

If it's a terminating error, the exit never gets called :( And, even if I try/catch and exit >0, if I call it with -File I lose the exit code.

grahamrhay Over a year ago

Hmm, your example works for me. And yet, my build is still green. I'll see if I can work out what's different.

Community · Accepted Answer · 2017-05-23 12:18:26Z

12

It is a known problem. Workarounds are calling the script with -File, using the -Command parameter (and adding ; exit $lastexitcode if you also have your own exit codes) or turning them into exit codes like Shay is showing or the example using trap below. See here for more information.

trap
{
    $ErrorActionPreference = "Continue";   
    Write-Error $_
    exit 1
}

$ErrorActionPreference = "Stop";   
$null.split()

edited May 23, 2017 at 12:18

CommunityBot

11 silver badge

answered Aug 23, 2013 at 22:10

Lars Truijens

43.9k6 gold badges134 silver badges146 bronze badges

1 Comment

Ola Eldøy Over a year ago

This workaround works well in Jenkins. I simply used the following Windows PowerShell command: PowerShell -File "srcipt.ps1"; exit $lastexitcode;

Collectives™ on Stack Overflow

How can I get powershell to return the correct exit code when called with the -File argument?

2 Answers 2

2 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related