Mark Waite added a comment - 2021-01-15 03:52 - edited jmcclain as far as I can tell from my test job, Jenkins 2.263.2 is correctly showing the failure of the example: node { powershell ''' throw 'Error! Problem Exists Between Keyboard And Chair' exit 0 # Unreachable code ''' } Can you check again?

Jeffrey McClain added a comment - 2021-01-15 19:41 - edited Just updated Jenkins to 2.263.2 and also updated all the plugins, same issue. The test code in your comment doesn't seem to match this issue precisely though, to elaborate: From https://www.jenkins.io/blog/2017/07/26/powershell-pipeline/ Section title: "Write to all available streams and return the standard output" node { def stdout = powershell(returnStdout: true , script: ''' # Enable streams 3-6 $WarningPreference = 'Continue' $VerbosePreference = 'Continue' $DebugPreference = 'Continue' $InformationPreference = 'Continue' Write-Output 'Hello, World!' Write-Error 'Something terrible has happened!' Write-Warning 'Warning! There is nothing wrong with your television set' Write-Verbose 'Do not attempt to adjust the picture' Write-Debug 'We will control the horizontal. We will control the vertical' Write-Information 'We can change the focus to a soft blur or sharpen it to crystal clarity.' ''') println stdout } The article states that running this code should result in the console output: ERROR: script returned exit code 1 Finished: FAILURE However, when I copy / paste this code verbatim into my pipeline script within Jenkins on Windows 10 ( https://i.imgur.com/8yYk7gE.png ) and run it, I get ( https://i.imgur.com/gsoCxq8.png): Finished: SUCCESS Could you please try simply copying / pasting the exact example code into your Jenkins instance and seeing if the pipeline shows a success or failure at the end? The point I'm trying to make is that the Jenkins article states this exact code should result in a failure, but in reality the code returns a success. I am not sure if the article is simply incorrect, if the Jenkins behaviour has changed since the article was written, etc.

Roberto added a comment - 2024-02-19 15:45 my 2 cents: seems to be related to  https://issues.jenkins.io/browse/JENKINS-63945?jql=resolution%20is%20EMPTY%20and%20component%3D16044 "Scripts now exit with $LastExitCode, causing non-zero exit codes to mark a build as failed"   But according to https://stackoverflow.com/questions/10666035/difference-between-and-lastexitcode-in-powershell this works only for external commands