[Insight-developers] Script for Remote Module testing

Bradley Lowekamp blowekamp at mail.nih.gov
Wed Jan 29 08:36:26 EST 2014


Hello,

I'm lazy and want to reduce the maintenance burden on creating a nightly build to test the remote modules.

It looks like the script running on "dash5.kitware" is nicely grinding through some remote modules ( and potentially other off by default modules like DCMTK, MINC). I was about to suggest this be some how added into the "dashboard" branch, but now I am seeing the itkmodular_common.cmake script there, which really has a lot of the functionality need such as some support for valgrind and coverage.

Does it make since to bring back the modular dashboard for these other modules?

I really just want to be able to specify a list for modules to be modularly tested on a a couple builds and try to re-use a script to do this. I am trying to figure out what's the easiest way to do this for the long run.

Thanks,
Brad


More information about the Insight-developers mailing list