[CMake] Build on one machine, test on multiple

[Martin Apel]

Hi Alok,

the problem is not to start the testing process remotely. In my case
it's no problem simply setting up the Windows task planner to execute
some script every night. The problem is more, how do I tell ctest to
perform its tests without having to perform the complete build as well.
I would probably need to copy both the complete source as well as the
binary directory from the build to the test machines and then have a
ctest script execute only the test and submit steps. For the binary
directory to be usable this would either require the directories being
under the same path on all machines or to modify the files in the build
directory somehow, so the paths are correct with respect to the test
machine.

Regards,

Martin

On 05/27/10 22:12, Alok Govil wrote:
> Hi Martin,
>
> This is of interest to me as well.  Please let me know what you find.
>
> Here are two ways I could find to start a task on a remote Windows
> computer:
>
>     http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
>     I do not know if the return code from the executable will be
> passed back by this utility.
>
>    
> http://motevich.blogspot.com/2007/11/execute-program-on-remote-computer.html
>     This seems to pass the return code back from the remote
> executable.  Requires a script
>     to run however, so I would prefer #1 if it solves the issue.
>
> I wonder if there is a platform independent way of doing this.
>
> Thanks,
>
> Alok
>
> > Date: Thu, 27 May 2010 14:41:11 +0200
> > From: martin.apel at simpack.de
> > To: cmake at cmake.org
> > Subject: [CMake] Build on one machine, test on multiple
> >
> > Hi all,
> >
> > we have currently set up a nightly build process, which builds and tests
> > our software via CMake / CTest and submits results to CDash.
> > However I would like run some tests on multiple machines with different
> > OS versions (Windows XP, Vista, Windows 7) for a build, which has been
> > created under Windows XP on a single machine. That means I explicitly
> > don't want to build the software on each machine, that it is tested on.
> > Has anybody else tried such a thing using CMake and CTest? If you have
> > any ideas on how to approach this, please let me know.
> >
> > Martin
> >
> > _______________________________________________
> > 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
>
> ------------------------------------------------------------------------
> The New Busy is not the too busy. Combine all your e-mail accounts
> with Hotmail. Get busy.
> <http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4>


-- 

Martin Apel                                    
Software Architect                              
Phone:   + 49 8105 77266-53
E-Mail:  martin.apel at simpack.de

SIMPACK AG
Friedrichshafener Strasse 1, 82205 Gilching, Germany
info at simpack.de, www.simpack.com
Phone: + 49 8105 77266-0
Fax:   + 49 8105 77266-11


Executive Board: Dr. Alexander Eichberger, Dr. Lutz Mauer
Chair of Supervisory Board: Silvia Förster (CPA)
Commercial Register München HRB 181 229

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100528/8971a395/attachment-0001.htm>