From ayoung at vigilos.com Sun Jul 1 19:29:54 2007 From: ayoung at vigilos.com (Alasdair Young) Date: Sun, 01 Jul 2007 16:29:54 -0700 Subject: [Cruisecontrolrb-users] Changing location of the Rakefile? Message-ID: <468838F2.7090801@vigilos.com> Hi. I have a simple problem: I use rake to run my build but my Rakefile is not in the root of my subversion trunk. Is there any way to convince cruisecontrol.rb to use a Rakefile in trunk/builds rather than in trunk? i.e. all I want is a simple "cd builds" before execution of my Rakefile begins. For strange, convoluted reasons, I can't simply move the Rakefile to the base of the trunk. The only way that I can see to do this is to write a 2-line shell script to cd to the appropriate directory and then run rake. Surely there is a way to specify the location of my Rakefile so I don't have to do this? (I am using 1.1.0 of cruisecontrol.rb) Any help would be greatly appreciated! (It's such a simple problem, and yet, all my solutions see ugly or messy.) - alasdair Alasdair Young Software Engineer Vigilos Inc. www.vigilos.com From ariddle at sunbridgecapital.com Mon Jul 2 16:16:14 2007 From: ariddle at sunbridgecapital.com (Allen Riddle) Date: Mon, 2 Jul 2007 15:16:14 -0500 Subject: [Cruisecontrolrb-users] Build isn't failing on "errors" Message-ID: <92667DFF6C174E4CB99320F328D7E87FB037E1@sbexchg.1stFinancialLeasing.com> Hello, I've set up CruiseControl.rb for our Rails app. The build is not failing even though the unit test in question actually contains a Ruby error (wrong number of arguments passed to a method). This doesn't come up as a "failure", but instead as an "error" when the unit test runs. Shouldn't CC.rb fail the build because of this? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070702/67c467e9/attachment.html From jeremystellsmith at gmail.com Tue Jul 3 00:39:29 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Mon, 2 Jul 2007 21:39:29 -0700 Subject: [Cruisecontrolrb-users] Build isn't failing on "errors" In-Reply-To: <92667DFF6C174E4CB99320F328D7E87FB037E1@sbexchg.1stFinancialLeasing.com> References: <92667DFF6C174E4CB99320F328D7E87FB037E1@sbexchg.1stFinancialLeasing.com> Message-ID: if your regular failures will fail the build, then it sounds like this might be a problem w/ test/unit or ruby. not sure what we could do about it if it was. can you reproduce the problem w/ a simple example? Jeremy On 7/2/07, Allen Riddle wrote: > > Hello, I've set up CruiseControl.rb for our Rails app. The build is not > failing even though the unit test in question actually contains a Ruby error > (wrong number of arguments passed to a method). This doesn't come up as a > "failure", but instead as an "error" when the unit test runs. Shouldn't > CC.rb fail the build because of this? Thanks. > > _______________________________________________ > 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/20070702/ba676a77/attachment.html From Derek.Wong at orionhealth.com Tue Jul 3 00:51:13 2007 From: Derek.Wong at orionhealth.com (Derek Wong) Date: Tue, 03 Jul 2007 16:51:13 +1200 Subject: [Cruisecontrolrb-users] Newby problem with CCRB 1.1.0 under Win XP: Can't bring up dashboard... Message-ID: <468A7E81.3702.00B7.0@orionhealth.com> Hi, I just started using CCRB 1.1.0 under a Win XP system today for the first time. So far I've been able to kick off the tests (Ruby/WATIR test scripts) with success. I can see that the tests run and a build.log/build_status.success file seems to indicate that things are okay. Whenever I try access the dashboard from IE or Firefox I get the following displayed on my web browser: Errno::EINVAL in Projects#index Showing app/views/projects/_project.rhtml where line #1 raised: Invalid argument - C:/cruisecontrolrb/projects/Watfo/builder.pid Extracted source (around line #1): 1:
2: 3: 4: Trace of template inclusion: /app/views/projects/index.rhtml RAILS_ROOT: ./script/../config/.. Application Trace | Framework Trace | Full Trace #{RAILS_ROOT}/lib/project_blocker.rb:24:in `flock' #{RAILS_ROOT}/lib/project_blocker.rb:24:in `blocked?' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:78:in `builder_down?' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:13:in `status' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:26:in `fatal?' #{RAILS_ROOT}/app/models/project.rb:183:in `last_complete_build_status' #{RAILS_ROOT}/app/views/projects/_project.rhtml:1:in `_run_rhtml_47app47views47projects47_project46rhtml' #{RAILS_ROOT}/app/views/projects/index.rhtml:6:in `_run_rhtml_47app47views47projects47index46rhtml' #{RAILS_ROOT}/app/views/projects/index.rhtml:5:in `each' #{RAILS_ROOT}/app/models/projects.rb:72:in `send' #{RAILS_ROOT}/app/models/projects.rb:72:in `method_missing' #{RAILS_ROOT}/app/views/projects/index.rhtml:5:in `_run_rhtml_47app47views47projects47index46rhtml' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `index' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `call' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `index' cruise:6:in `load' cruise:6:in `start' cruise:66:in `send' cruise:66 #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `compile_and_render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:301:in `render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:260:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:275:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:59:in `render_partial' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:58:in `benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:58:in `render_partial' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:287:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `compile_and_render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:301:in `render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:260:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:806:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:738:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:863:in `render_without_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:798:in `render_action' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:748:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:747:in `silence' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:747:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/layout.rb:244:in `render_without_benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `measure' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:163:in `respond' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:161:in `each' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:161:in `respond' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:105:in `respond_to' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:1095:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:1095:in `perform_action_without_filters' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:632:in `call_filter' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:619:in `perform_action_without_benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `measure' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/rescue.rb:83:in `perform_action' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `process_without_filters' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:624:in `process_without_session_management_support' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/session_management.rb:114:in `process' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:330:in `process' #{RAILS_ROOT}/vendor/rails/railties/lib/dispatcher.rb:41:in `dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:113:in `handle_dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:79:in `service' c:/ruby/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' c:/ruby/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' c:/ruby/lib/ruby/1.8/webrick/server.rb:155:in `start_thread' c:/ruby/lib/ruby/1.8/webrick/server.rb:144:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:144:in `start_thread' c:/ruby/lib/ruby/1.8/webrick/server.rb:94:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:89:in `each' c:/ruby/lib/ruby/1.8/webrick/server.rb:89:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:79:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:79:in `start' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:63:in `dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/commands/servers/webrick.rb:59 c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `new_constants_in' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' #{RAILS_ROOT}/vendor/rails/railties/lib/commands/server.rb:40 c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' script/server:46 #{RAILS_ROOT}/lib/project_blocker.rb:24:in `flock' #{RAILS_ROOT}/lib/project_blocker.rb:24:in `blocked?' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:78:in `builder_down?' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:13:in `status' #{RAILS_ROOT}/builder_plugins/installed/builder_status.rb:26:in `fatal?' #{RAILS_ROOT}/app/models/project.rb:183:in `last_complete_build_status' #{RAILS_ROOT}/app/views/projects/_project.rhtml:1:in `_run_rhtml_47app47views47projects47_project46rhtml' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `compile_and_render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:301:in `render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:260:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:275:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:59:in `render_partial' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:58:in `benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/partials.rb:58:in `render_partial' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:287:in `render' #{RAILS_ROOT}/app/views/projects/index.rhtml:6:in `_run_rhtml_47app47views47projects47index46rhtml' #{RAILS_ROOT}/app/views/projects/index.rhtml:5:in `each' #{RAILS_ROOT}/app/models/projects.rb:72:in `send' #{RAILS_ROOT}/app/models/projects.rb:72:in `method_missing' #{RAILS_ROOT}/app/views/projects/index.rhtml:5:in `_run_rhtml_47app47views47projects47index46rhtml' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:326:in `compile_and_render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:301:in `render_template' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_view/base.rb:260:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:806:in `render_file' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:738:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:863:in `render_without_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:798:in `render_action' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:748:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:747:in `silence' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:747:in `render_with_no_layout' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/layout.rb:244:in `render_without_benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `render' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `measure' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:50:in `render' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `index' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `call' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:163:in `respond' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:161:in `each' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:161:in `respond' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/mime_responds.rb:105:in `respond_to' #{RAILS_ROOT}/app/controllers/projects_controller.rb:7:in `index' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:1095:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:1095:in `perform_action_without_filters' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:632:in `call_filter' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:619:in `perform_action_without_benchmark' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `measure' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/rescue.rb:83:in `perform_action' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `send' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `process_without_filters' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/filters.rb:624:in `process_without_session_management_support' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/session_management.rb:114:in `process' #{RAILS_ROOT}/vendor/rails/actionpack/lib/action_controller/base.rb:330:in `process' #{RAILS_ROOT}/vendor/rails/railties/lib/dispatcher.rb:41:in `dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:113:in `handle_dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:79:in `service' c:/ruby/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' c:/ruby/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' c:/ruby/lib/ruby/1.8/webrick/server.rb:155:in `start_thread' c:/ruby/lib/ruby/1.8/webrick/server.rb:144:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:144:in `start_thread' c:/ruby/lib/ruby/1.8/webrick/server.rb:94:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:89:in `each' c:/ruby/lib/ruby/1.8/webrick/server.rb:89:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:79:in `start' c:/ruby/lib/ruby/1.8/webrick/server.rb:79:in `start' #{RAILS_ROOT}/vendor/rails/railties/lib/webrick_server.rb:63:in `dispatch' #{RAILS_ROOT}/vendor/rails/railties/lib/commands/servers/webrick.rb:59 c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `new_constants_in' #{RAILS_ROOT}/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' #{RAILS_ROOT}/vendor/rails/railties/lib/commands/server.rb:40 c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' script/server:46 cruise:6:in `load' cruise:6:in `start' cruise:66:in `send' cruise:66 Request Parameters: None Show session dump --- Response Headers: {"cookie"=>[], "Content-Type"=>"text/html", "Cache-Control"=>"no-cache"} Cruise logs the following to the console: C:\cruisecontrolrb>cruise start --trace => Booting WEBrick... => Rails application started on http://0.0.0.0:3333 => Ctrl-C to shutdown server; call with --help for options [2007-07-03 15:54:22] INFO WEBrick 1.3.1 [2007-07-03 15:54:22] INFO ruby 1.8.2 (2004-12-25) [i386-mswin32] [2007-07-03 15:54:22] INFO WEBrick::HTTPServer#start: pid=2120 port=3333 [debug] Loading plugin builder_status [debug] Loading plugin email_notifier [debug] Loading plugin minimal_console_logger [debug] Loading plugin project_logger [info] [2007-07-03 15:54:28] Builder for project 'Watfo' started Logging to: C:/cruisecontrolrb/log/Watfo_builder.log [debug] [2007-07-03 15:54:28] Polling source control [debug] C:/cruisecontrolrb/projects/Watfo/work autotest$ svn --non-interactive l og --revision HEAD:113 --verbose --xml [debug] [2007-07-03 15:54:29] No new revisions detected [debug] [2007-07-03 15:54:29] Sleeping 127.0.0.1 - - [03/Jul/2007:15:54:37 New Zealand Standard Time] "GET / HTTP/1.1" 500 15911 - -> / 127.0.0.1 - - [03/Jul/2007:15:55:04 New Zealand Standard Time] "GET / HTTP/1.1" 500 15911 - -> / [debug] [2007-07-03 15:59:34] Polling source control [debug] C:/cruisecontrolrb/projects/Watfo/work autotest$ svn --non-interactive l og --revision HEAD:113 --verbose --xml [debug] [2007-07-03 15:59:35] No new revisions detected [debug] [2007-07-03 15:59:35] Sleeping 127.0.0.1 - - [03/Jul/2007:16:02:32 New Zealand Standard Time] "GET / HTTP/1.1" 500 15911 - -> / [debug] [2007-07-03 16:04:40] Polling source control [debug] C:/cruisecontrolrb/projects/Watfo/work autotest$ svn --non-interactive l og --revision HEAD:113 --verbose --xml [debug] [2007-07-03 16:04:42] No new revisions detected [debug] [2007-07-03 16:04:42] Sleeping By the way I am running Ruby 1.8.2, Watir 1.5.1.1192, rake 0.7.3 and rails 1.2.3. Thanks to anyone out there who can enlighten me on this issue. Getting pretty pages from the dashboard would be great! Regards, Derek Wong. From duff.john at gmail.com Tue Jul 3 14:03:22 2007 From: duff.john at gmail.com (jduff) Date: Tue, 3 Jul 2007 11:03:22 -0700 (PDT) Subject: [Cruisecontrolrb-users] File.cp command problem Message-ID: <11417653.post@talk.nabble.com> I have two tasks, one that runs the tests and another that copies and sets up the config files. the task that runs the tests depends on the task that copies the files. For some reason the tests get run before the copy commands get executed when run under cruise, run from command line (by copying the ruby rake execution that cruise uses) it works fine. A couple example tasks: task :cruise_build => :task1 do puts "cruise build" end task :task1 => :task2 do puts "task 1" end task :task2 do puts "task2" cp 'config/solr.yml.template', 'config/solr.yml' cp 'config/database.yml.template', 'config/database.yml' cp 'config/memcache.yml.template', 'config/memcache.yml' end Command line output: task2 cp config/solr.yml.template config/solr.yml cp config/database.yml.template config/database.yml cp config/memcache.yml.template config/memcache.yml task 1 cruise build Cruise Output: task2 task 1 cruise build cp config/solr.yml.template config/solr.yml cp config/database.yml.template config/database.yml cp config/memcache.yml.template config/memcache.yml This is a problem since I need these files prepared before doing anything else. Any help with this issue at all would really be appreciated. -- View this message in context: http://www.nabble.com/File.cp-command-problem-tf4019999.html#a11417653 Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com. From Derek.Wong at orionhealth.com Tue Jul 3 21:08:05 2007 From: Derek.Wong at orionhealth.com (Derek Wong) Date: Wed, 04 Jul 2007 13:08:05 +1200 Subject: [Cruisecontrolrb-users] Newby problem with CCRB 1.1.0 under Win XP: Can't bring up dashboard... Message-ID: <468B9BB6.3702.00B7.0@orionhealth.com> Just trawled through the logs and documentation again this morning, turns out that CCRB requires Ruby 1.8.4 or greater (duh! it was mentioned too...) while I'm using Ruby 1.8.2. This may be contributing to or is the root cause of the dashboard problem although it would otherwise seem that the builder component of CCRB works just fine with Ruby 1.8.2. Problem is that I can't just move up to Ruby 1.8.4/1.8.5 because the tests I'm running rely on a Ruby 1.8.2/Watir 1.5.1.1192 to test modal dialogs present in the web application. So it looks like I could be stuck on this one. Is there another way? Regards, Derek W. >>> "Derek Wong" 3/07/2007 4:51 p.m. >>> [Previous logs and description deleted] From ketanpadegaonkar at gmail.com Wed Jul 4 00:55:51 2007 From: ketanpadegaonkar at gmail.com (Ketan Padegaonkar) Date: Wed, 04 Jul 2007 10:25:51 +0530 Subject: [Cruisecontrolrb-users] Newby problem with CCRB 1.1.0 under Win XP: Can't bring up dashboard... In-Reply-To: <468B9BB6.3702.00B7.0@orionhealth.com> References: <468B9BB6.3702.00B7.0@orionhealth.com> Message-ID: <468B2857.30906@gmail.com> > Just trawled through the logs and documentation again this morning, tur= ns out that CCRB requires Ruby 1.8.4 or greater (duh! it was mentioned to= o...) while I'm using Ruby 1.8.2. This may be contributing to or is the = root cause of the dashboard problem although it would otherwise seem that= the builder component of CCRB works just fine with Ruby 1.8.2. >=20 > Problem is that I can't just move up to Ruby 1.8.4/1.8.5 because the te= sts I'm running rely on a Ruby 1.8.2/Watir 1.5.1.1192 to test modal dialo= gs present in the web application. So it looks like I could be stuck on = this one. >=20 > Is there another way? You could try running this on jruby, jruby is 1.8.5 compatible (Although I've never tried running cc.rb on jruby). Alternatively you could install Ruby 1.8.5 instance in another folder, and use that instance to run ruby. > Regards, > Derek W. --=20 Ketan Padegaonkar I blog... therefore I am... http://ketan.padegaonkar.name/ C:\> WIN Bad command or filename C:\> LOSE Loading Microsoft Windows ... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070704/9d0a8019/attachment.bin From Derek.Wong at orionhealth.com Wed Jul 4 22:41:41 2007 From: Derek.Wong at orionhealth.com (Derek Wong) Date: Thu, 05 Jul 2007 14:41:41 +1200 Subject: [Cruisecontrolrb-users] Newby problem with CCRB 1.1.0 under Win XP: Can't bring up dashboard... In-Reply-To: <468B2857.30906@gmail.com> References: <468B9BB6.3702.00B7.0@orionhealth.com> <468B2857.30906@gmail.com> Message-ID: <468D0340.3702.00B7.0@orionhealth.com> Thanks to those out there who gave suggestions. In the end I've just parallel installed Ruby 1.8.2 and 1.8.5. I now have CCRB running under RB 1.8.5 and my Web tests running against Ruby 1.8.2/WATIR 1.5.1.1192. I've now explicitly path to the 1.8.2 install of Ruby to execute my web tests. This seems to work fine and the dashboard now appears as expected. Not an optimal solution but definitely workable, now I just need to get the ci_reporter XML files processed into something that CCRB can display. Regards, Derek. >>> Ketan Padegaonkar 4/07/2007 4:55 p.m. >>> > Just trawled through the logs and documentation again this morning, tur= ns out that CCRB requires Ruby 1.8.4 or greater (duh! it was mentioned to= o...) while I'm using Ruby 1.8.2. This may be contributing to or is the = root cause of the dashboard problem although it would otherwise seem that= the builder component of CCRB works just fine with Ruby 1.8.2. >=20 > Problem is that I can't just move up to Ruby 1.8.4/1.8.5 because the te= sts I'm running rely on a Ruby 1.8.2/Watir 1.5.1.1192 to test modal dialo= gs present in the web application. So it looks like I could be stuck on = this one. >=20 > Is there another way? You could try running this on jruby, jruby is 1.8.5 compatible (Although I've never tried running cc.rb on jruby). Alternatively you could install Ruby 1.8.5 instance in another folder, and use that instance to run ruby. > Regards, > Derek W. --=20 Ketan Padegaonkar I blog... therefore I am... http://ketan.padegaonkar.name/ C:\> WIN Bad command or filename C:\> LOSE Loading Microsoft Windows ... From Derek.Wong at orionhealth.com Thu Jul 5 23:28:59 2007 From: Derek.Wong at orionhealth.com (Derek Wong) Date: Fri, 06 Jul 2007 15:28:59 +1200 Subject: [Cruisecontrolrb-users] CCRB and ci_reporter XML output: How do you display custom build artifacts Message-ID: <468E5FCD.3702.00B7.0@orionhealth.com> Hi, I've installed ci_reporter (having previously installed CruiseControlRB), as both a gem and a rails plugin. The tests are invoked by an explicit project.command (rake ci:setup:testunit test - I probably shouldn't need to do this explicitly but I'm semi-following ci_reporter instructions here) from cruise_config.rb. At the completion of the tests I see XML files generated in my work/test/reports directory but what further set up do to CruiseControlRB or ci_reporter do I need to create a custom build artifacts build report generated from this XML as an HTML page showing on the dashboard? The dashboard looks okay as it stands but it'd be nice to get a more comprehensive test report from the XML. Thanks. Regards, Derek. From ariddle at sunbridgecapital.com Fri Jul 6 11:23:16 2007 From: ariddle at sunbridgecapital.com (Allen Riddle) Date: Fri, 6 Jul 2007 10:23:16 -0500 Subject: [Cruisecontrolrb-users] Build isn't failing on "errors" Message-ID: <92667DFF6C174E4CB99320F328D7E87FB037E5@sbexchg.1stFinancialLeasing.com> Thanks Tim. After doing some digging, it turns out that Ruby 1.8.6 doesn't return an error code if there is an exception raised in an at_exit block. This is exactly what Test::Unit does. So does the rake task you created work around this? Thanks for your help. ________________________________ From: Tim Lucas [mailto:t.lucas at gmail.com] Sent: Tuesday, July 03, 2007 12:29 AM To: Jeremy Stell-Smith Cc: Allen Riddle; cruisecontrolrb-users at rubyforge.org Subject: Re: [Cruisecontrolrb-users] Build isn't failing on "errors" On 03/07/2007, at 2:39 PM, Jeremy Stell-Smith wrote: On 7/2/07, Allen Riddle wrote: Hello, I've set up CruiseControl.rb for our Rails app. The build is not failing even though the unit test in question actually contains a Ruby error (wrong number of arguments passed to a method). This doesn't come up as a "failure", but instead as an "error" when the unit test runs. Shouldn't CC.rb fail the build because of this? Thanks. if your regular failures will fail the build, then it sounds like this might be a problem w/ test/unit or ruby. The build must return an error exit code. If it does not, then CC.rb does not consider it failed. If it's within your own rake task you simply need to 'raise': http://pastie.textmate.org/75604 -- tim -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070706/49c7cb7e/attachment.html From javadragon at gmail.com Fri Jul 6 12:32:04 2007 From: javadragon at gmail.com (Lori Olson) Date: Fri, 6 Jul 2007 10:32:04 -0600 Subject: [Cruisecontrolrb-users] Build isn't failing on "errors" In-Reply-To: <92667DFF6C174E4CB99320F328D7E87FB037E5@sbexchg.1stFinancialLeasing.com> References: <92667DFF6C174E4CB99320F328D7E87FB037E5@sbexchg.1stFinancialLeasing.com> Message-ID: Alex helped us with this same issue. We ended up going with his advice, and installing Ruby 1.8.5 for use by CC. It works. On 7/6/07, Allen Riddle wrote: > > Thanks Tim. After doing some digging, it turns out that Ruby 1.8.6doesn't return an error code if there is an exception raised in an at_exit > block. This is exactly what Test::Unit does. So does the rake task you > created work around this? Thanks for your help. > > > ------------------------------ > > *From:* Tim Lucas [mailto:t.lucas at gmail.com] > *Sent:* Tuesday, July 03, 2007 12:29 AM > *To:* Jeremy Stell-Smith > *Cc:* Allen Riddle; cruisecontrolrb-users at rubyforge.org > *Subject:* Re: [Cruisecontrolrb-users] Build isn't failing on "errors" > > > > On 03/07/2007, at 2:39 PM, Jeremy Stell-Smith wrote: > > On 7/2/07, *Allen Riddle* wrote: > > Hello, I've set up CruiseControl.rb for our Rails app. The build is not > failing even though the unit test in question actually contains a Ruby error > (wrong number of arguments passed to a method). This doesn't come up as a > "failure", but instead as an "error" when the unit test runs. Shouldn't > CC.rb fail the build because of this? Thanks. > > > > if your regular failures will fail the build, then it sounds like this > might be a problem w/ test/unit or ruby. > > > > The build must return an error exit code. If it does not, then CC.rb does > not consider it failed. > > > > If it's within your own rake task you simply need to 'raise': > > http://pastie.textmate.org/75604 > > > > -- tim > > > > _______________________________________________ > 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/20070706/753d2da0/attachment-0001.html From lambda77 at gmail.com Tue Jul 10 18:00:28 2007 From: lambda77 at gmail.com (Lambda SeventySeven) Date: Tue, 10 Jul 2007 18:00:28 -0400 Subject: [Cruisecontrolrb-users] A few questions about CruiseControl.rb Message-ID: I'm using CruiseControl.rb on Windows Server 2003 and have found it to be extremely useful. I have a few questions, for which I wasn't able to find answers elsewhere. 1) Is there a service version of "cruise start" for Windows? What I'd like to achieve is to have cruise start at startup. In fact my server gets rebooted sometimes, and I'd love to have cruise up and running when it reboots. 2) I've setup the email notification, by specifying my gmail user credentials and the notification emails, but unfortunately no emails have ever been sent. Analyzing the logs I've not found anything related to email attempts which failed. 3) It is probably out of the scope of CruiseControl.rb, but I'd like to use it in connection to a local working copy of the repository. Every time CruiseControl.rb detects a successful build, it should run a svn up on a given local folder, though this shouldn't be the case if the build were to fail. I can hack something together to obtain this functionality, but I'd like some pointers as to where I should look in order to get started with this. Thanks in advance, Lambda. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070710/42d1c652/attachment.html From thibaut.barrere at gmail.com Tue Jul 10 18:47:50 2007 From: thibaut.barrere at gmail.com (=?ISO-8859-1?Q?Thibaut_Barr=E8re?=) Date: Wed, 11 Jul 2007 00:47:50 +0200 Subject: [Cruisecontrolrb-users] A few questions about CruiseControl.rb In-Reply-To: References: Message-ID: <4a68b8cf0707101547t19703053i3cc7c06a9725db3f@mail.gmail.com> Hi, here's a couple of tips that may help: > 1) Is there a service version of "cruise start" for Windows? What I'd like to achieve is to have cruise start at startup. In fact my server gets rebooted sometimes, and I'd love to have cruise up and > running when it reboots. Not sure if there is something built-in in cc.rb for that purpose. You may want to have a look at http://www.duodata.de/ntwrapper/ - I'm using it for one SVN repository which is started as a service on a W2K server. Alternatively I've also been using cygwin which provides helpers to boot any command line as a service too (but It's a bit heavier to download). > 2) I've setup the email notification, by specifying my gmail user credentials and the notification emails, but unfortunately no emails have ever been sent. Analyzing the logs I've not found anything related > to email attempts which failed. Did you configure the smtp server in your ~cruise/config/site_config.rb (I suppose so) ? Can the smtp host name be resolved from that machine ? Can you try with a deliberately wrong password to see if something happens ? > 3) It is probably out of the scope of CruiseControl.rb, but I'd like to use it in connection to a local working copy of the repository. Every time CruiseControl.rb detects a successful build, it should run a > svn up on a given local folder, though this shouldn't be the case if the build were to fail. I can hack something together to obtain this functionality, but I'd like some pointers as to where I should look in > order to get started with this. ccnet.rb is good at calling rake, and with rake it's easy to call a svn up on a specific folder. Are you using rake ? You could achieve what you describe with something similar to: task :build do # do what you need to build end task :deploy => :build do Dir.chdir('c:/website') throw "Failure while updating my website!" unless system('svn up') end I've been using this a lot with CruiseControl.Net a lot (like: compiling asp.net applications, packaging them, runnings tests, then deploying to an internal staging server if the build is successful) cheers, Thibaut Barr?re -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070711/b04a3dcc/attachment.html From grant.mcinnes at ehealthinnovation.org Mon Jul 16 19:26:32 2007 From: grant.mcinnes at ehealthinnovation.org (Grant McInnes) Date: Mon, 16 Jul 2007 19:26:32 -0400 Subject: [Cruisecontrolrb-users] remote builders Message-ID: <245B327E-567F-4DA0-AE9E-35D6F63335F9@ehealthinnovation.org> 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 From RRussell at thoughtworks.com Mon Jul 16 20:10:54 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 16 Jul 2007 19:10:54 -0500 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: <245B327E-567F-4DA0-AE9E-35D6F63335F9@ehealthinnovation.org> Message-ID: 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 ' 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 before calling ssh. If you do the work feel free to submit a patch. --Rolf Grant McInnes 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 From manish at gslab.com Wed Jul 18 01:07:59 2007 From: manish at gslab.com (Manish Sapariya) Date: Wed, 18 Jul 2007 10:37:59 +0530 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: References: Message-ID: <469DA02F.8040306@gslab.com> 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 > ' > > 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 > before calling ssh. > If you do the work feel free to submit a patch. > > --Rolf From RRussell at thoughtworks.com Wed Jul 18 11:30:26 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Wed, 18 Jul 2007 10:30:26 -0500 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: <469DA02F.8040306@gslab.com> Message-ID: 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 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 > ' > > 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 > 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 From manish at gslab.com Thu Jul 19 01:07:58 2007 From: manish at gslab.com (manish) Date: Thu, 19 Jul 2007 10:37:58 +0530 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: References: Message-ID: <469EF1AE.3030908@gslab.com> 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 From RRussell at thoughtworks.com Thu Jul 19 10:34:18 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Thu, 19 Jul 2007 09:34:18 -0500 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: <469EF1AE.3030908@gslab.com> Message-ID: 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 07/19/2007 12:07 AM To Rolf Russell , 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 From averkhov at thoughtworks.com Thu Jul 19 15:39:01 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 19 Jul 2007 14:39:01 -0500 Subject: [Cruisecontrolrb-users] remote builders In-Reply-To: <469DA02F.8040306@gslab.com> Message-ID: 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 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 > ' > > 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 > 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 From jmerv at corp.earthlink.net Mon Jul 23 15:47:49 2007 From: jmerv at corp.earthlink.net (Joshua Mervine) Date: Mon, 23 Jul 2007 12:47:49 -0700 Subject: [Cruisecontrolrb-users] CruiseControl.rb with CVS Message-ID: Is it possible to use CruiseControl.rb with cvs? I couldn't find any docs on it. Thanks. --Josh From jeremystellsmith at gmail.com Tue Jul 24 11:48:38 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Tue, 24 Jul 2007 08:48:38 -0700 Subject: [Cruisecontrolrb-users] CruiseControl.rb with CVS In-Reply-To: References: Message-ID: not currently, but there are a few people that have successfully hacked in support to different vcs's. CVS is close enough to Subversion that it should be relatively straitforward if you're feeling brave :) On 7/23/07, Joshua Mervine wrote: > > Is it possible to use CruiseControl.rb with cvs? I couldn't find any > docs on it. Thanks. > > --Josh > > > > _______________________________________________ > 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/20070724/1840d49b/attachment.html From ketanpadegaonkar at gmail.com Tue Jul 24 12:07:54 2007 From: ketanpadegaonkar at gmail.com (Ketan Padegaonkar) Date: Tue, 24 Jul 2007 21:37:54 +0530 Subject: [Cruisecontrolrb-users] [ANN] CCTray written in Java to connect to Cruise Control Message-ID: Hi, JCCTray is a Java port of CCTray that was originally written in .NET. JCCTray is a utility for use with all flavors of CruiseControl Continuous Integration servers. Specifically it works with CruiseControl, CruiseControl.NET, CruiseControl.Rb. It provides feedback on build progress, and allows control over some of the server's operations. You can download JCCTray from http://jcctray.sourceforge.net/ Cheers, Ketan Padegaonkar I blog... Therefore I am... http://ketan.padegaonkar.name