That's a great idea for a feature request. It's probably not feasible with out-of-the-box CVS, but you could certainly come up with an implementation of it for svn or any revision control system with atomic commits of multiple file changes at once.<br>
<br><div>You could probably get fancy with a script that does a custom update step and track the svn revision number yourself, and only allow it to increment one at a time.</div><div><br></div><div><br></div><div>Good luck. Let us know if you get something working... A script that does this would make for a good article on the CMake Wiki.</div>
<div><br><div><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 10:13 AM, no spam <span dir="ltr"><<a href="mailto:nospam@degarrah.com">nospam@degarrah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi, <br>Is there a way to tell ctest to only update to the next revision? I use cmake+cdash for our build system and I would really like to get a build for every commit if possible. <br>Thank you,<br><font color="#888888">NS<br>
</font><br>_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br></div></div>