Pipeline one-liner causes hanging job ?

[Torsten Reinhard]

Hi all,

when starting to work with Pipelines a tested this simple script:

// should fail - nothing else
assert false

This caused my Pipeline Job to hang - so I have to kill it.

When writing more complex code I ran more than once into this "hanging pipeline" problem - no output, no stactrace and you can only "system out" debug it step by step....

Can anyone explain why that happens ?

Thanx, and best regards,
Torsten

[nco...@fgtsa.com]

This caused my Pipeline Job to hang - so I have to kill it. 

 

As mentioned in this issue, you can use as workaround

assert false : 'oh no!'

Not sure if the resolution was already released.