Has anyone done anything towards remote builders yet? I don''t suppose its gonna be too hard to do, what with drb and friends on my side, but if someone has put something together, or has pointers to a good way to script win32 boxes to start up arbitrary GUI apps, I would be mucho obligado. -g
It shouldn''t be hard. I haven''t had a chance to do it yet but
have seen
things like:
project.build_command = ''ssh bob at remotebox
./home/run_build.sh
<REVISION>''
where the code is checked out both on the ccrb box and on the remote box.
ccrb figures out the revision when it is triggered and then passes it to a
shell script on the remotebox that checks out to that revision and runs
the build.
run_build.sh:
#/bin/bash
svn up -r$1
rake
The trick is that ccrb doesn''t know how to figure out the revision yet.
You''ll need to substitute the revision number for <REVISION>
before
calling ssh.
If you do the work feel free to submit a patch.
--Rolf
Grant McInnes <grant.mcinnes at ehealthinnovation.org>
Sent by: cruisecontrolrb-users-bounces at rubyforge.org
07/16/2007 06:26 PM
To
cruisecontrolrb-users at rubyforge.org
cc
Subject
[Cruisecontrolrb-users] remote builders
Has anyone done anything towards remote builders yet? I don''t
suppose its gonna be too hard to do, what with drb and friends on my
side, but if someone has put something together, or has pointers to a
good way to script win32 boxes to start up arbitrary GUI apps, I
would be mucho obligado.
-g
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users at rubyforge.org
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070716/915b0ffe/attachment.html
Would n''t it be possible to have some daemon like thing running on remote machine, which is drb or custom protocol based. Ssh does not work (out of the box) when remote windows is machine. My problem is that I want to run unit tests on multiple platforms in one of my build configuration. Thanks, Manish Rolf Russell wrote:> > It shouldn''t be hard. I haven''t had a chance to do it yet but have > seen things like: > > project.build_command = ''ssh bob at remotebox ./home/run_build.sh > <REVISION>'' > > where the code is checked out both on the ccrb box and on the remote > box. ccrb figures out the revision when it is triggered and then > passes it to a shell script on the remotebox that checks out to that > revision and runs the build. > > run_build.sh: > #/bin/bash > svn up -r$1 > rake > > The trick is that ccrb doesn''t know how to figure out the revision > yet. You''ll need to substitute the revision number for <REVISION> > before calling ssh. > If you do the work feel free to submit a patch. > > --Rolf
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. 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. 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. --Rolf Manish Sapariya <manish at gslab.com> Sent by: cruisecontrolrb-users-bounces at rubyforge.org 07/18/2007 12:07 AM To cruisecontrolrb-users at rubyforge.org cc Subject Re: [Cruisecontrolrb-users] remote builders Would n''t it be possible to have some daemon like thing running on remote machine, which is drb or custom protocol based. Ssh does not work (out of the box) when remote windows is machine. My problem is that I want to run unit tests on multiple platforms in one of my build configuration. Thanks, Manish Rolf Russell wrote:> > It shouldn''t be hard. I haven''t had a chance to do it yet but have > seen things like: > > project.build_command = ''ssh bob at remotebox ./home/run_build.sh > <REVISION>'' > > where the code is checked out both on the ccrb box and on the remote > box. ccrb figures out the revision when it is triggered and then > passes it to a shell script on the remotebox that checks out to that > revision and runs the build. > > run_build.sh: > #/bin/bash > svn up -r$1 > rake > > The trick is that ccrb doesn''t know how to figure out the revision > yet. You''ll need to substitute the revision number for <REVISION> > before calling ssh. > If you do the work feel free to submit a patch. > > --Rolf_______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070718/1ab99e1f/attachment-0001.html
Rolf Russell wrote:> > 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. > > 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. > 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.What I am thinking of is some kind of abstraction layer, may be in rake, where in we just say a given task is to be executed on remote machine, by specifying some attributes, e.g. IP, Port in case of RDB or host, username and password in case of ssh. We also assume that the remote machine has all the necessary requirement fulfilled to execute given task. I am not sure if this is really a CCRB item or a rake item, but in a given typical scenario, I want some of my tests to run on windows machine and the report should be retrieved back for on CCRB. E.g. Some of my watir test has to run on Windows machine, where as my CCRB is hosted on Unix machine. So for me turning off those watir tests is the only option for CCRB build to report success. Hope this make sense. Thanks and Regards, Manish
Hi Manish, I say give ssh or drb a shot and tell us what happens. I think both approaches are reasonable. I''m not convinced about the value of an abstraction layer over both ssh & drb. I''m more of a get-one-of-them-to-work-and-then-see type of guy. BTW - does anyone else have a solution around the pains of ssh on windows? --Rolf manish <manish at gslab.com> 07/19/2007 12:07 AM To Rolf Russell <RRussell at thoughtworks.com>, cruisecontrolrb-users at rubyforge.org cc Subject Re: [Cruisecontrolrb-users] remote builders Rolf Russell wrote:> > 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. > > 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. > 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.What I am thinking of is some kind of abstraction layer, may be in rake, where in we just say a given task is to be executed on remote machine, by specifying some attributes, e.g. IP, Port in case of RDB or host, username and password in case of ssh. We also assume that the remote machine has all the necessary requirement fulfilled to execute given task. I am not sure if this is really a CCRB item or a rake item, but in a given typical scenario, I want some of my tests to run on windows machine and the report should be retrieved back for on CCRB. E.g. Some of my watir test has to run on Windows machine, where as my CCRB is hosted on Unix machine. So for me turning off those watir tests is the only option for CCRB build to report success. Hope this make sense. Thanks and Regards, Manish -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070719/ed4e3ad7/attachment.html
Hi, There is a couple of ways to have sshd on a Windows box. Cygwin is the most obvious, and I think there is an inexpensive (to the tune of $40) commercial solution. One can also write a really simple web app that does this. Botom line: it''s not a hard problem to roll your own solution for, and there are not many enough CC.rb users who need it, so it doesn''t seem to be a good core feature to me. -- Alex Manish Sapariya <manish at gslab.com> Sent by: cruisecontrolrb-users-bounces at rubyforge.org 07/17/2007 11:07 PM To cruisecontrolrb-users at rubyforge.org cc Subject Re: [Cruisecontrolrb-users] remote builders Would n''t it be possible to have some daemon like thing running on remote machine, which is drb or custom protocol based. Ssh does not work (out of the box) when remote windows is machine. My problem is that I want to run unit tests on multiple platforms in one of my build configuration. Thanks, Manish Rolf Russell wrote:> > It shouldn''t be hard. I haven''t had a chance to do it yet but have > seen things like: > > project.build_command = ''ssh bob at remotebox ./home/run_build.sh > <REVISION>'' > > where the code is checked out both on the ccrb box and on the remote > box. ccrb figures out the revision when it is triggered and then > passes it to a shell script on the remotebox that checks out to that > revision and runs the build. > > run_build.sh: > #/bin/bash > svn up -r$1 > rake > > The trick is that ccrb doesn''t know how to figure out the revision > yet. You''ll need to substitute the revision number for <REVISION> > before calling ssh. > If you do the work feel free to submit a patch. > > --Rolf_______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070719/505203d4/attachment.html