com.wellsfargo.cdpipeline.deploy.udeploy.UCDCodeStation::push:40 Exception

Problem: (See data below) Looks like the jenkins-pipeline-ucd-plugin requires the Jenkins Pipeline Build Status to not be a "FAILURE" for UCD Code Status Push & Deploy to proceed. It throws the following hudson.AbortException and fails the pipeline. Our question is if there any workaround for this to accommodate the continuation of the pipeline execution as core Jenkins does not put a hard stop on a pipeline with Build Status to not be a "FAILURE" ? Would you be able to release a new version to relax this hard stop so that UCD deployment can proceed for alternate scenarios in pre-production environments?

******************************
Code: https://github.com/jenkinsci/ibm-ucdeploy-pipeline-plugin/blob/master/src/main/java/com/urbancode/jenkins/plugins/ucdeploy/UCDeployPublisher.java#L478

if (build.getResult() == Result.FAILURE || build.getResult() == Result.ABORTED) {
throw new AbortException("Skip artifacts upload to IBM UrbanCode Deploy - build failed or aborted.");
}


******************************
Error: hudson.AbortException
:
:
com.urbancode.jenkins.plugins.ucdeploy.UCDeployPublisher.perform(UCDeployPublisher.java:481)
11:53:23
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
11:53:23
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
11:53:23
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
11:53:23
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
11:53:23
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11:53:23
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
11:53:23
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
11:53:23
at java.lang.Thread.run(Thread.java:748)[Less]