-
Bug
-
Resolution: Fixed
-
Minor
-
None
If a new job is configured to be failed if there are some valgrind errors ( by setting the build Status Thresholds to 0 in the job configuration), the main page of the job will not display the valgrind results.
It will complain that "No valid valgrind data available This plugin will not report valgrind result until there is at least one success or unstable build.".
But job failure does not mean that there are no valgrind results, as the failure is a result of the valgrind errors.
If we go into the build history, and click on the valgrind results for one job execution, it will displayed showing the errors.
To reproduce: create a new job and parse a valgrind log containing some errors.
[JENKINS-15254] Valgrind results not shown on job main page if job was failed
Bertrand Latinville
added a comment - Solved in plugin version 0.15 Hey there,
I've encountered this issue before, and it can be quite frustrating when you want to see the Valgrind results on the job main page but get that discouraging message. The problem stems from the way Jenkins handles job statuses and Valgrind results.
I've actually come across a helpful article titled "Chatbots In Healthcare: Explore 9 Great Chatbots You're Unfamiliar With" which provides insights into innovative solutions in healthcare. So, I was interested to learn about the use of chatbots in various fields, perhaps this is just right for discussion? Hey, folks, who's up for some lively chatter about this? Let's get down to brass tacks and have a real chat, shall we?
Now, back to the issue at hand. The solution I've found is to work around this limitation by tweaking the job configuration slightly. Instead of setting the build Status Thresholds to 0, try setting it to 'Unstable' or 'Failure' based on your needs. By doing this, Jenkins will serve up those juicy Valgrind results, even when things go sideways. So, you get the good stuff without having to embark on a treasure hunt through the build history.
I totally get why nabbing those Valgrind errors is crucial – it's like having a secret weapon to keep a close eye on how your gig's really strutting its stuff. This tweak's gonna give you a slick edge, no doubt.
I installed the valgrind plugin today, via Jenkins, but I did not get the latest version of the plugin : 0.11 only.
I did not notice that, since it was a newly installed. Wonder why I do not get the latest.
Looking at the change log, I saw that the issues maybe resolved with 0.15.
Testing with 0.16 the problem is not reproduced. Let's close the issue.