-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.222.4
Valgrind Plug-in 0.28
openjdk 11.0.7 2020-04-14
Ubuntu 18.04.4 LTS
I generate Valgrind xml report via MakeFile, then I use Valgrind plugin to display results:
stage('Valgrind') {
steps {
echo 'Static code check..'
sh '''
mkdir -p build
cd build
make valgrind
'''
publishValgrind (
failBuildOnInvalidReports: false,
failBuildOnMissingReports: false,
failThresholdDefinitelyLost: '',
failThresholdInvalidReadWrite: '',
failThresholdTotal: '',
pattern: 'build/valgrind/valgrind_memcheck.xml',
publishResultsForAbortedBuilds: false,
publishResultsForFailedBuilds: false,
sourceSubstitutionPaths: '',
unstableThresholdDefinitelyLost: '',
unstableThresholdInvalidReadWrite: '',
unstableThresholdTotal: ''
)
}
}
With freshly created job I am able to see Valgrind Trend, but after triggering job few more times Valgrind Trend is not displayed and in Jenkins logs I can see an error:
2020-06-09 07:50:30.732+0000 [id=64] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://10.1.0.48:8080/job/pipeline/valgrindResult/graph java.lang.NullPointerException
[JENKINS-62627] Valgrind Trend is not displayed
I have seen this same issue with Jenkins 2.334.
I narrowed down the problem to occur when I have forced Git commits in the pipeline. Clean/proper sequential Git commit history or associated pipeline history seems to be OK. Hopefully that gives a clue to the developers of this component.
Mine is a new project, I have not pushed too many changes, so the original description of this ticket is more valuable.
Deniz Eren
added a comment - - edited I have seen this same issue with Jenkins 2.334.
I narrowed down the problem to occur when I have forced Git commits in the pipeline. Clean/proper sequential Git commit history or associated pipeline history seems to be OK. Hopefully that gives a clue to the developers of this component.
Mine is a new project, I have not pushed too many changes, so the original description of this ticket is more valuable. 
I have the same error with :
Jenkins 2.222.3
Valgrind plugin 0.28
openjdk version "1.8.0_212"
alpine 3.9.4
It is really annoying as it is a showstopper to make it adopted by supported teams.