What steps will reproduce the problem?
1. Make a pipeline that refers to a pipeline stage that is not defined
2. try to run it
> What is the expected output? What do you see instead?
Expect a nice error message explaining that the pipeline stage couldn't be
found. Instead see a giant groovy error stack trace.
Original issue reported on code.google.com by ssade...@gmail.com on 16 Jul 2012 at 3:18
Original issue reported on code.google.com by
ssade...@gmail.com
on 16 Jul 2012 at 3:18