Status: Closed (View Workflow)
Nodes and Processes v2.17
Durable Task v1.15
Declarative Pipeline v1.2.2
Jenkins master is running on a windows 10 machine
When I run the following pipeline on a test jenkins instance running on my PC, it always returns successful:
Here is the console output:
This blog post states that any of these actions in powershell should trigger a failed build (throw an exception, return exit code != 0, write to error stream, set lastexitcode !=0). In fact, none of them are triggering it, I have tried each individually.
I tried this on our production Jenkins machine, and it did trigger a failed build (expected behavior). This machine is running:
Declarative Pipeline v1.1.9
Nodes and Processes v2.13
Durable Task v1.14
Machine is a Linux Slave, and the pipeline got executed on a Windows 7 slave. Therefore, I don't know whether this bug is caused by the newer version on my test setup, by the fact that it gets executed on the master, or by the OS differences.
I am marking this as major because a pipeline falsely marked as Successful in production could be a major problem.