Setup a valgrind job on Jenkins

[Russell Taylor]

Jenkins has a valgrind plugin. It seems like it would be interesting to make use of this to run valgrind over some of our unit tests and (hopefully) get the results presented in a nice way. Of course it might be really slow so we probably can't do everything.

Start out trying to get it working with Kernel, Geometry, API and maybe DataObjects.

Early tests already show that something needs fixing to allow the KernelTest executable to be run directly, as we'll need to do for valgrind.

[Russell Taylor]

Re #7657. Reset the config to the default at the start.

Running the KernelTest executable directly showed that a previous test had changed it so this test failed.

Changeset: 97b00b4f6e6ba552c86134b9c42bc0e489f0386c

[Russell Taylor]

Re #7657. Correct indentation: tabs -> spaces.

Changeset: 289967508bb14e926b49cd61ae324a708019aca8

[Russell Taylor]

Re #7657. Make tests pass when APITest executable is run directly.

Changeset: 659726bec2267b1907e7e4266a071372f64b05fe

[Russell Taylor]

The Jenkins job is at ​https://builds.sns.gov/job/ornl_valgrind_develop/.

The small changes in the feature/7657_jenkins_valgrind_job branch were so that test executables could be run directly rather than via ctest.

At the moment, this just runs the Kernel, Geometry & API tests. There's an issue with the DataObjects test executable that needs fixing before that can be used - see #7674.

There's plenty showing up in the current job to be going on with before we think about running over more test targets. That could also lead to a very long-running job!

[Peter Peterson]

This was done correctly. My only question is if it should also be done on master.

[Stuart Campbell]

This ticket has been transferred to github issue ​8502