Re-consider what I mentioned earlier today, Slicer source should still be checked out from SVN. This is important for extensions support.

Correction: VVN source: git
Slicer source: svn

WIP branch -- all the user has to do in the template script is define GIT_REPOSITORY
https://github.com/chrismullins/Slicer/commit/50a6ade150ef8b5706e80c70e0344c7866325262

There could be a GIT_TAG variable defined so that the vvn-master branch is checked out if GIT_REPOSITORY is defined, executing the command:
git clone -b vvn-master git@kwsource.kitwarein.com:ninja/vvn.git ${CTEST_SOURCE_DIRECTORY}
Or, just checkout VVN repo by default (if GIT_REPOSITORY), setting GIT_TAG to "".

See https://github.com/chrismullins/Slicer/commit/50a6ade150ef8b5706e80c70e0344c7866325262#commitcomment-1516082

I agree with your comments.

https://github.com/chrismullins/Slicer/commit/b0a80e5165fec59ff0b8186582bf94bd9ba63810

Updated so that GIT_TAG corresponds with only the branch name desired by the user.

https://github.com/chrismullins/Slicer/commit/7c3d5ce1626b99b78b03485081e35a97c3841c0a

Is there any need to check whether or not the "-b" option is available (as in Visomics and CMake), or can we assume everyone is using a suitable version of git?

TODO: Make sure updating works, don't clone a new repo every night.

See inlined comment. Thanks

For my reference: http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest

This appears to work: https://github.com/chrismullins/Slicer/commit/5c7218f0d5180fdb4fb20b00ee7dd632b17a3801

Below is some ctest output after resetting HEAD a few times:

Updating the repository: /home/crmullin/Dashboards/Slicer4
Use GIT repository type
Old revision of repository is: aaac769daf04b7a67d21ecc47db3ad920af1019a
New revision of repository is: ce84477eb44d8975995db7d6f86ac712bd8b81ae
Gathering version information (one . per revision):
..
Found 1 updated files

Consider note: https://github.com/chrismullins/Slicer/commit/5c7218f0d5180fdb4fb20b00ee7dd632b17a3801#commitcomment-1522420

Thanks for the catch.
https://github.com/chrismullins/Slicer/commit/399675abb668b32785c5d222e3930e4fab49313b

I was wondering which it would be according to http://www.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Style_Guide#Commit_message_prefix

Commit message updated to match guidelines.

https://github.com/chrismullins/Slicer/commit/81e9ae63faed04bd972fd1f4b7e74eefad32c7f4

Make sure you get github commit on your kitware account. In the mean time, consider reading: https://github.com/chrismullins/Slicer/commit/81e9ae63faed04bd972fd1f4b7e74eefad32c7f4#commitcomment-1529474

Fixed in r20549

See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20549

Both Slicer nightly and continuous dashboard works as expected, the new driver script works fine.