[JIRA] [workflow-plugin] (JENKINS-32099) Using StringBuilder in Workflow makes failing build without warning

[jgl...@cloudbees.com (JIRA)]

Title: Message Title

Jesse Glick resolved as Not A Defect   Please provide a complete, self-contained test case to reproduce. After I ran a fresh 1.642, installed Workflow: Aggregator with the required restart, made a new flow with the text supplied, commented out your phony git step, and also commented out the JUnitResultArchiver step, I got org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.lang.StringBuilder which looks right to me. Perhaps you meant to fix the test step to delete testDataPublishers: [] which does not work (filed elsewhere), in which case you get Started by user anonymous [Workflow] Allocate node : Start Running on master in /…/workspace [Workflow] node { [Workflow] archive [Workflow] step Recording test results [Workflow] } //node [Workflow] Allocate node : End [Workflow] End of Workflow ERROR: No test report files were found. Configuration error? Finished: FAILURE which is correct behavior—it is your script which is foolishly doing something in a finally block, which if it fails will mask any earlier error. (And it will fail, because there are no test results yet, pending an RFE in junit.) If you want to archive failing test results, ask Gradle to return a zero exit code in case tests ran but failed. You could also use the catchError step. If you really want it is also possible to call Throwable.addSuppressed, though in this case it is tricky since AbortException stack traces are not printed, so you would need a wrapper exception: def err try { executeGradle('clean test') } catch (_err) { err = _err } finally { try { archive '**/*' step([$class: 'JUnitResultArchiver', keepLongStdio: false, testResults: '**/build/test-results/*.xml']) } catch (_err) { if (err != null) { def x = new Exception(_err) x.addSuppressed(err) throw x } else { throw _err } } } (Of course in this case you need to approve a couple more signatures for the exotic error handling.) Jenkins / JENKINS-32099 Using StringBuilder in Workflow makes failing build without warning Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.