Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-24562

Publish Valgrind results and ClearCase


    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • valgrind-plugin
    • None
    • rhel 6.3 and ClearCase

      The ClearCase version control system works by spawning a subshell in "view context". (This is something like chroot). The correct version of files are not available until a view is set. I.e., the file /path/to/source/main.cpp is different depending on which view i set.

      The "Publish Valgrind results" post-build action does not handle this. Wrong version of the source file seems to be copied as seen by the "[Valgrind] copying source file...] log statements. So when clicking on a memory issue in the results wrong version of the file is presented.

      However, files can also be accessed by their abosolute path in /view/myviewname/path/to/source/main.cpp. So, if the plugin could offer an optional "prefix path" which if set was prepended to the from file in the abovementioned copy i think this would help.

            existence Johannes Ohlemacher
            knutpett Knut Petter S
            1 Vote for this issue
            3 Start watching this issue