On 6/8/2016 12:59 PM, Bartlett, Roscoe A wrote:
Xavier,
Thanks for the info. I got another email from Brad King and he also
pointed out the same thing:
https://cmake.org/cmake/help/v3.6/command/ctest_start.html#command:ctest_start
and then Brad updated the documentation for ctest_update() to state that
it will just keep you on whatever tracking branch you are on and do a
git pull (after doing a reset --hard to wipe out any local changes).
With is info, I can do what I need.
If you have something external like jenkins doing the build, you can
also use:
https://cmake.org/cmake/help/latest/variable/CTEST_UPDATE_VERSION_ONLY.html?highlight=ctest_update_version_only
If set in the ctest script the ctest_update command will just get the
hash and do nothing else.
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
