Hi David,<br><br>Yes, that helps somewhat, thank you! I get it to now use svn and I'm ignore the <a href="http://kitware.com">kitware.com</a> trigger mentions as you advise that its not actually doing the upload.<br><br>
Continuous and Experimental cdash submissions seem to go through; I'm assuming my nightly one is breaking, where it seems to try to zip back to revision 0 and gets confused since there are no files there, because I don't have a repository from "yesterday". I assume tomorrow my nightly test will automagically begin working if it finds a more recent revision in the right time range.<br>
<br> Old revision of repository is: 5<br>* Update repository: "/opt/subversion/bin/svn" info<br>D impl<br>D tests<br>D include<br>D CTestConfig.cmake<br>D CMakeLists.txt<br>Updated to revision 0.<br>
Problem determining the current revision of the repository from output:<br>D impl<br>D tests<br>D include<br>D CTestConfig.cmake<br>D CMakeLists.txt<br>Updated to revision 0.<br><br>And I fully intend to buy a copy of the book.. once I convince myself with some simple tests that its worth dumping time and energy into a full eval of cmake on our full hairy source tree. Obvious bootstrapping problem but I need to look at a few different systems to narrow a shortlist before spending money right now.<br>
<br>thanks again<br>b.<br><br><br><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 12:41 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Don't worry... it's not submitting results to Kitware, it's using a default value for CTEST_TRIGGER_SITE, which is old and leftover from pre-CDash days... It used to be the case that after all results were uploaded, a "trigger" script would run to tell the server to process the previously uploaded files. CDash processes files as they are submitted so triggers are not necessary with CDash. I actually fixed this very code in ctest earlier today to avoid trigger calls when using CDash. (See changes listed here: <a href="http://www.cdash.org/CDash/viewUpdate.php?buildid=263494" target="_blank">http://www.cdash.org/CDash/viewUpdate.php?buildid=263494</a>)<br>
<br><div>To answer your questions:</div><div>The CMake book has a Tutorial chapter in it that takes you through the steps involved in adding CTest / CDash support to your CMake based project. If you have the book, read through the Tutorial chapter... it's pretty quick. If you don't have the book, buy it. :-) (You can also check out the code that goes with the chapter in the CMake/Tests/Tutorial/Step1 through Step7 directories in a CMake source tree...)</div>
<div><br></div><div>Basically, you need to call ENABLE_TESTING() and INCLUDE(CTest) in your CMakeLists.txt file.</div><div><br></div><div>And yes, "make test" returns errors when there are test failures...</div>
<div><br></div><div><div>And you should set CTEST_UPDATE_COMMAND to the full path to the svn executable to use svn instead of cvs...</div><div><br></div><div><br></div><div>HTH,</div><div>David</div><br></div></blockquote>
</div><br>