<br><font size=2 face="sans-serif">I started looking at using cygwin to
provide ssh in windows a few weeks ago but got side tracked and didn't
finish. I would recommend starting by looking into that.</font>
<br>
<br><font size=2 face="sans-serif">It would be possible to have a daemon/agent
running on the remote machine. I've shyed away from this because
ssh was such a simple solution and I didn't have time.</font>
<br><font size=2 face="sans-serif">It may also be possible to simply run
cruise on the remote machine and use a shared file system to have the main
instance of cruise report the results from all remote machines. There
are likely issues to be worked out with showing when a build is running,
forcing builds, etc.</font>
<br>
<br><font size=2 face="sans-serif">--Rolf</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Manish Sapariya <manish@gslab.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: cruisecontrolrb-users-bounces@rubyforge.org</font>
<p><font size=1 face="sans-serif">07/18/2007 12:07 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">cruisecontrolrb-users@rubyforge.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Cruisecontrolrb-users] remote builders</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Would n't it be possible to have some daemon like
thing running on remote<br>
machine, which is drb or custom protocol based.<br>
<br>
Ssh does not work (out of the box) when remote windows is machine.<br>
<br>
My problem is that I want to run unit tests on multiple platforms in one
of<br>
my build configuration.<br>
<br>
Thanks,<br>
Manish<br>
<br>
<br>
Rolf Russell wrote:<br>
><br>
> It shouldn't be hard. I haven't had a chance to do it yet but
have <br>
> seen things like:<br>
><br>
> project.build_command = 'ssh bob@remotebox
./home/run_build.sh <br>
> <REVISION>'<br>
><br>
> where the code is checked out both on the ccrb box and on the remote
<br>
> box. ccrb figures out the revision when it is triggered and
then <br>
> passes it to a shell script on the remotebox that checks out to that
<br>
> revision and runs the build.<br>
><br>
> run_build.sh:<br>
> #/bin/bash<br>
> svn up -r$1<br>
> rake<br>
><br>
> The trick is that ccrb doesn't know how to figure out the revision
<br>
> yet. You'll need to substitute the revision number for <REVISION>
<br>
> before calling ssh. <br>
> If you do the work feel free to submit a patch.<br>
><br>
> --Rolf<br>
<br>
_______________________________________________<br>
Cruisecontrolrb-users mailing list<br>
Cruisecontrolrb-users@rubyforge.org<br>
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users<br>
</font></tt>
<br>