[ITK Community] [Insight-developers] CTest ctest_submit in parts, re-running

[Bradley Lowekamp]

David,

Thanks for the information.

(1) You mean delete the build manually on CDash

(2) Regarding the second approach, I thought something like the following psudo-ctest code would achieve that:

ctest_start()
ctest_update()
ctest_configure()
ctest_build()
ctest_submit(PARTS Start Update Configure Build)
ctest_test()
ctest_build( TARGET dist APPEND)
ctest_submit(PARTS Build)

But the builds reporting on the dashboard was very odd. With a green 0+5 in the warnings, and the warnings showing up some places but not others. Is this the backwards compatible mode you referred to in you blog entry?

I'll likely take you advice in just adding (1) option one, but I after spending this much time on the issue, I'd like to complete my understanding.

Thanks,
Brad




On Feb 25, 2014, at 12:20 PM, David Cole <dlrdave at aol.com> wrote:

> I think you have two options:
> 
> (1) delete the build manually before re-running the script
> 
> Easy, but manual.
> 
> (2) Do a ctest_submit of a ctest_build Build.xml file without the APPEND...
> 
> When you submit the Build.xml file without APPEND in it is the *only* trigger for CDash to delete a build first before adding the new information being submitted.
> 
> This second technique could be automated, but it would result in a (probably even more) confusing script.
> 
> I'd recommend going with (1) unless you really, really need it automated.
> 
> 
> D
> 

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Kitware offers ITK Training Courses, for more information visit:
http://kitware.com/products/protraining.php

Please keep messages on-topic and check the ITK FAQ at:
http://www.itk.org/Wiki/ITK_FAQ

Follow this link to subscribe/unsubscribe:
http://www.itk.org/mailman/listinfo/insight-developers