Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-03-22 Thread Tyler Roscoe
Following up on this thread: http://public.kitware.com/pipermail/cmake/2010-February/035197.html It's not as elegant as I would like -- support for ctest_update(... APPEND ...) would be much cleaner, but I didn't have the bandwidth to take on that project at this time -- but I believe I have a hac

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-18 Thread Tyler Roscoe
On Thu, Feb 18, 2010 at 11:21:39AM -0500, David Cole wrote: > It's not that the code would be trickier, it's that the CDash database > schema only supports one view of a repository in terms of generating correct > links on its update report pages. So even if ctest allowed you to do this, > CDash wo

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-18 Thread David Cole
It's not that the code would be trickier, it's that the CDash database schema only supports one view of a repository in terms of generating correct links on its update report pages. So even if ctest allowed you to do this, CDash would not produce correct output. There's a lot *more* work to be don

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-18 Thread Tyler Roscoe
On Thu, Feb 18, 2010 at 09:14:05AM -0500, David Cole wrote: > The APPEND option is probably a little more complicated than you think it > is... And it is not "secretly" (or otherwise) added to ctest_update... > CMake, being open source and all, has no secrets. :-) I was just joking about it being

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-18 Thread David Cole
The APPEND option is probably a little more complicated than you think it is... And it is not "secretly" (or otherwise) added to ctest_update... CMake, being open source and all, has no secrets. :-) We need to write some docs or an article that explains how to use "APPEND" well. Every call to cte

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-17 Thread Tyler Roscoe
On Wed, Feb 17, 2010 at 04:16:15PM -0700, Clinton Stimpson wrote: > On 02/17/2010 03:49 PM, Tyler Roscoe wrote: > >On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote: > > > >>Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra > >>arguments for > >>updating the way yo

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-17 Thread Clinton Stimpson
On 02/17/2010 03:49 PM, Tyler Roscoe wrote: On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote: Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments for updating the way you want? This affects the svn update command itself (which is working fine wit

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-17 Thread Tyler Roscoe
On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote: > Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments > for > updating the way you want? This affects the svn update command itself (which is working fine without further adjustment) but does not appear to a

Re: [CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-17 Thread Clinton Stimpson
Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments for updating the way you want? Clint On Wednesday 17 February 2010 02:45:17 pm Tyler Roscoe wrote: > I've got a preliminary Continuous Integration system up and running > based on the scripts Bill pointed me to. Thanks B

[CMake] CTEST_UPDATE_COMMAND vs sparse working copy (was Re: continuous integration with CMake)

2010-02-17 Thread Tyler Roscoe
I've got a preliminary Continuous Integration system up and running based on the scripts Bill pointed me to. Thanks Bill! I have some questions about this setup. Let me know if you think I would get better responses on the CDash list. I'm going to break up these questions into separate posts to ho