![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Johannes Ohlemacher
|
|
Components:
|
valgrind |
|
Created:
|
13/Aug/14 8:19 PM
|
|
Description:
|
I've been using the valgrind publisher in an environment where
valgrind under some circumstances is not executed correctly leading to either missing, or malformed xml files.
Under normal conditions, valgrind reports errors for the project rather rarely (and the trend usually is at 0 for several builds).
This leads to a situation where errors can be missed, because it's not
easily visible if valgrind reported 0 errors, or if the publisher failed to read the valgrind output.
Hence, I've got a suggestion to improve the publisher plugin:
Would it be possible to add an option which fails the build in case no valgrind xml reports were found, or if one or more reports couldn't be parsed.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Christian Fetzer
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
