[CMake] multiple cvs updates for continuous build
David Cole
david.cole at kitware.com
Thu Jul 2 15:26:44 EDT 2009
When used with CDash, last one wins.
CTest overwrites the contents of Update.xml whenever a ctest_update step is
performed. So... whichever update step should be reported to CDash is the
one you should prefer as the last one...
On Thu, Jul 2, 2009 at 3:10 PM, Bram de Greve
<bramz at users.sourceforge.net>wrote:
> Clinton Stimpson wrote:
>
>> You can do it like this:
>>
>> ....
>> WHILE (${CTEST_ELAPSED_TIME} LESS 36000)
>> SET (START_TIME ${CTEST_ELAPSED_TIME})
>> CTEST_START (Continuous)
>> CTEST_UPDATE (SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE res1)
>> CTEST_UPDATE (SOURCE "${OTHER_SOURCE_DIRECTORY}" RETURN_VALUE res2)
>> IF(res1 GREATER 0 OR res2 GREATER 0)
>> CTEST_CONFIGURE()
>> CTEST_BUILD()
>> CTEST_TEST()
>> CTEST_SUBMIT()
>> ....
>>
>>
>> Clint
>>
>> Thanks Clint, I'll try this tomorrow!
> When used with CDash, will this combine the reported update?
>
> Bram
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20090702/da9fc8ae/attachment-0001.htm>
More information about the CMake
mailing list