[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-51091 Make test results available on currentBuild Change By: Andrew Bayer Component/s: workflow-support-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Sam Van Oort commented on JENKINS-51091 Re: Make test results available on currentBuild Red flag for me: if we do off-master, this one would add some nontrivial extra complexity to that implementation. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title
Sean MacKay commented on JENKINS-51091
Re: Make test results available on currentBuild
Interesting, so do none of the test results pages in normal or Blue Ocean UI function without the junit plugin? Or is the way the data is eventually saved into the finished build just even harder to access? I assumed the workaround with AbstractTestResultAction pulled the results from the same final location which both nunit and junit post to, but I haven't tested to confirm so I'm not sure. And that's interesting. I assume you could use it in a scripting pipeline like this. Does the same work in Declarative pipeline?
def results = junit '*.xml';
sh "echo ${results.getFailCount()}"
Unfortunately the `nunit` plugin doesn't seem to behave the same way (I use both). Yet it still posts the results to the same final place, so those results should still be available from one location regardless of which plugin posts there. That's why I assumed there would be a way to read them, but I don't know enough about the architecture in place to really be sure of anything. I'll do some testing and see if I can at least confirm what the behaviour of each approach is.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Andrew Bayer commented on JENKINS-51091 Re: Make test results available on currentBuild It'd be at least a little complicated - the workflow-support plugin would need to depend on the junit plugin, etc. For what it's worth, the junit step does return a TestResultSummary. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Sean MacKay created an issue Jenkins / JENKINS-51091 Make test results available on currentBuild Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2018-05-02 20:05 Priority: Minor Reporter: Sean MacKay Currently, as described here, the only way to get the archived test results in a Pipeline job is through the currentBuild.rawBuild object and pulling an AbstractTestResultAction out of it to read test results. This involved whitelisting several external methods. This is a lot of work to try and say, generate a slack message saying "Build BUILD failed, X/Y tests failed". How hard would it be to define a property on the currentBuild Global Variable live this: currentBuild.testResult.failCount ? Add Comment
