-
Improvement
-
Resolution: Fixed
-
Minor
-
None
It appears through our trial usage so far that a lot of the meta data that is gathered from the valgrind plugin occurs only if the runner is used (and not just the reporter).
Many of the tests we instrument have command line arguments that need to be passed to them and the valgrind runner portion of the plugin does not appear to support such a concept.
Is this something that can be added?
[JENKINS-15139] Add ability to handle command line arguments in valgrind runner
Code changed in jenkins
User: Johannes Ohlemacher
Path:
src/main/java/org/jenkinsci/plugins/valgrind/ValgrindBuilder.java
src/main/resources/org/jenkinsci/plugins/valgrind/ValgrindBuilder/config.jelly
http://jenkins-ci.org/commit/valgrind-plugin/17bef8c049d3eb525dd66c6436d326964a2a7888
Log:
added support for arbitrary valgrind options (JENKINS-15139)
added support for program options (JENKINS-15138)
Johannes Ohlemacher
added a comment - fixed with release 0.12 
adding command line options for the program under test is on my todo list for quite some time, just give me a few more days.
thanks for the feedback!
btw: the runner prints the call to valgrind to the log (including all valgrind command line options),
so if you want to run valgrind by yourself (from your Makefile or whatever) and you miss some meta data, take a look at it! maybe you just missed some options!?