Failed Stage Indicating Weirdly in Web UI about jenkins-client-plugin HOT 7 CLOSED

hey @stevekuznetsov - Given the contents of that message, starting with the ; appearing, then the AbortException is thrown here

At that point, how the UI renders is in the hands of the pipeline code, and beyond the scope of the openshift client plugin. Perhaps it has something to do with the use of step { ... script { ...

And throwing the Abort per everything we've seen is the right thing to do.

If there is doubt that the abort exception is being thrown, and if this is at all reproducible, you can temporarily but a try/catch around the apply to confirm.

@jupierce - any additional thoughts or items you think I might be overlooking?

from jenkins-client-plugin.

If this is an error on the GUI side of things -- where should I report it?

from jenkins-client-plugin.

Per https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin I would follow the "Issue tracking" link which takes you to https://issues.jenkins-ci.org and the blue ocean category.

Aside from confirming the AbortException was thrown which I mentioned previously beforehand, as a heads up, I bet they are going to ask for a simplified test case for them to repro with, full logs, etc.

from jenkins-client-plugin.

Going to go ahead and close ... of course reopen if new evidence like the AbortException not getting thrown emerges.

from jenkins-client-plugin.

It looks like something is catching the exception and printing it out instead of allowing the job to fail.

The message you are seeing is constructed here and just the content of the AbortException: https://github.com/openshift/jenkins-client-plugin/blob/master/src/main/resources/com/openshift/jenkins/plugins/OpenShiftDSL.groovy#L729

This has traditionally been enough to stop a pipeline from executing. Perhaps declarative syntax handles exceptions differently?

What happens if you put an
error( "This should stop the job")
in your script somewhere? Is that exception swallowed as well?

ref: https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-error-code-error-signal

from jenkins-client-plugin.

thanks @jupierce - the OpenShiftDSL.groovy link you posted lines up with the one I posted in #32 (comment)

some goes wrt the new syntax and possible exception handling ...i.e. step { .. script {...

so all good on those points (thanks again) :-)

Didn't know about error(...) ... thanks for the tip / I agree a good sanity check for @stevekuznetsov to try.

If error(...) kills the job and throwing AbortException does not, then I suppose we use this bug to switch client plugin and OpenShiftDLS.groovy to use error(...) .... agree ?

from jenkins-client-plugin.

Though it is interesting that the doc for that step says: You can also just throw new Exception(), but this step will avoid printing a stack trace.

from jenkins-client-plugin.