and before the

id="project_PROJECT_NAME" class="project build_success"> which > causes a " Line 55, Column 65: document type does not allow element > "div" here." So the difference in the number of projects turned out to be key. The problem lies in app/views/projects/index.rhtml and is triggered by greater than five projects. In this case the extra table element is generated and the invalid xhtml seems to be causing the bad behavior. Regards, Lee From phlip2005 at gmail.com Tue Mar 18 11:20:25 2008 From: phlip2005 at gmail.com (Phlip) Date: Tue, 18 Mar 2008 08:20:25 -0700 Subject: [Cruisecontrolrb-users] [ANN] rake stats charts for CC.rb Message-ID: CCers: http://www.oreillynet.com/ruby/blog/2008/03/cruisecontrol_charts.html That "architectural spike" adds Gnuplot charts of 'rake stats' outputs to a new view, such as http://localhost:3333/projects/statistics/lemmings New question: How to productize this, as a plugin? A full Rails plugin, with generators to add controllers and views, seems to be overkill! -- Phlip From thewoolleyman at gmail.com Tue Mar 18 13:21:46 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Tue, 18 Mar 2008 10:21:46 -0700 Subject: [Cruisecontrolrb-users] [ANN] rake stats charts for CC.rb In-Reply-To: References: Message-ID: On Tue, Mar 18, 2008 at 8:20 AM, Phlip wrote: > New question: How to productize this, as a plugin? A full Rails plugin, with > generators to add controllers and views, seems to be overkill! Nice. Could it be a ccrb plugin? From phlip2005 at gmail.com Tue Mar 18 13:57:54 2008 From: phlip2005 at gmail.com (Phlip) Date: Tue, 18 Mar 2008 10:57:54 -0700 Subject: [Cruisecontrolrb-users] [ANN] rake stats charts for CC.rb In-Reply-To: References: Message-ID: <47E002A2.8060603@gmail.com> Chad Woolley wrote: >> New question: How to productize this, as a plugin? A full Rails plugin, with >> generators to add controllers and views, seems to be overkill! > Nice. Could it be a ccrb plugin? A builder_plugins/ plugin? I (briefly) didn't see a way to wedge in a new action. The long round-trip, which I alluded to, is a Rails plugin with a generator that deltas a new action into the existing controller. Etc. Nuking a gnat... I could move all the extensions to one file, then ask the user to require 'statistician' to pull everything in. Then if CC itself had a system to pull in registered plugins, the user could get the feature by moving statistician.rb into the /installed/ folder. And installing gnuplot.rb and Gnuplot. (-; -- Phlip http://assert2.rubyforge.org/ From will.sargent at gmail.com Thu Mar 27 12:30:19 2008 From: will.sargent at gmail.com (Will Sargent) Date: Thu, 27 Mar 2008 09:30:19 -0700 Subject: [Cruisecontrolrb-users] Conflicting database schema between projects on cc.rb Message-ID: Hi all, I'm running into an issue with the way that my Rails projects are organized. I have two projects, which are "staging" -- the current release branch "trunk" -- the mainline The issue I'm running into is that a database schema change has been made against trunk. This broke some of my integration tests that run against the database. Because both staging and trunk have the same database.yml file, they're working against the same database schema. I tried tweaking the test database of staging, but the way that Rails prepares the test database is to make a clone from the development one. So in order to run integration tests, I have to create a development database for staging that I'm never going to use. I ran into this with the regular java cruisecontrol server. I was using Spring, so I had a properties file that was specified by a system property I set through the command line. I'm not sure what the equivalent Rails / Ruby way is to do it, or what I do after that. Anyone done this themselves or have any ideas? Will. From averkhov at thoughtworks.com Thu Mar 27 15:43:18 2008 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 27 Mar 2008 14:43:18 -0500 Subject: [Cruisecontrolrb-users] Conflicting database schema between projects on cc.rb Message-ID: CI builds that run simultaneously should have absolutely nothing in common. Here is how I would do it: 1. Have two separate Rails environments (with different database settings), e.g. cruise_trunk and cruise_staging. 2. Set RAILS_ENV accordingly, before invoking Rake. 3. Forget about the development database altogether, and use something like db:migrate:reset instead, for the CI build. This can be done by adding something like this at the end of your Rakefile: if ENV['RAILS_ENV'] =~ /cruise_/ %w(test:units test:functionals test:integration).each do |task_name| Rake::Task[task_name].dependencies.delete('db:test:prepare') Rake::Task[task_name].dependencies << 'db:migrate:reset' end end On the trunk of CC.rb, we now have an option to prevent builds from running simultaneously altogether. This is not in a released version yet. -- Alex From will.sargent at gmail.com Fri Mar 28 21:41:24 2008 From: will.sargent at gmail.com (Will Sargent) Date: Fri, 28 Mar 2008 18:41:24 -0700 Subject: [Cruisecontrolrb-users] Conflicting database schema between projects on cc.rb In-Reply-To: References: Message-ID: On Thu, Mar 27, 2008 at 12:43 PM, Alexey Verkhovsky wrote: > CI builds that run simultaneously should have absolutely nothing in common. > Here is how I would do it: > Cool, thank you. I'll try that and see how it goes. Will. From jnaor at elbit.co.il Mon Mar 31 02:57:37 2008 From: jnaor at elbit.co.il (Jonathan Naor) Date: Mon, 31 Mar 2008 09:57:37 +0300 Subject: [Cruisecontrolrb-users] cruisecontrol.rb with C++ projects Message-ID: <1206946657.5890.29.camel@dp23406> Hi, This has probably been asked a hundred times, but I couldn't find the answer: how do I configure cruisecontrol.rb to build a c/c++ makefile? Thanks This e-mail message has been sent by Elbit Systems Ltd. and is for the use of the intended recipients only. The message may contain privileged or commercially sensitive information . If you are not the intended recipient you are hereby notified that any use, distribution or copying of this communication is strictly prohibited, and you are requested to delete the e-mail and any attachments and notify the sender immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080331/8878e6da/attachment.html From bkimble at inc21.com Mon Mar 31 14:07:05 2008 From: bkimble at inc21.com (Billy Kimble) Date: Mon, 31 Mar 2008 11:07:05 -0700 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? Message-ID: Guys, I recently installed CruiseControl and I love it. So much that I want to run it on its own server to handle all of my building needs. I installed it, added projects, ran it, and everything was groovy. I decided to stick the process in the background via: ./cruise start & And it put it in the background just fine too. Everything was kosher until I tried logging out of my server. CruiseControl seemed to not want to relinquish control of my SSH connection. I thought perhaps it was a fluke on my connection so I just forcefully disconnected and tried triggering CC to build, which failed with the following message: [error] Input/output error [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:20:in `write' [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:20:in `puts' [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:20:in `new_revisions_detected' [error] ./script/../config/../app/models/project.rb:325:in `send' [error] ./script/../config/../app/models/project.rb:325:in `notify' [error] ./script/../config/../app/models/project.rb:323:in `collect' [error] ./script/../config/../app/models/project.rb:323:in `notify' [error] ./script/../config/../app/models/project.rb:208:in `build_if_necessary' [error] ./script/../config/../app/models/polling_scheduler.rb:13:in `run' [error] ./script/builder:79 [error] ./script/builder:78:in `catch' [error] ./script/builder:78 [error] script/../config/../cruise:14:in `load' [error] script/../config/../cruise:14:in `builder' [error] script/../config/../cruise:68:in `send' [error] script/../config/../cruise:68 [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' [error] script/../config/../cruise:67 [error] Input/output error [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:24:in `write' [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:24:in `puts' [error] ./script/../config/../builder_plugins/installed/ minimal_console_logger.rb:24:in `build_loop_failed' [error] ./script/../config/../app/models/project.rb:325:in `send' [error] ./script/../config/../app/models/project.rb:325:in `notify' [error] ./script/../config/../app/models/project.rb:323:in `collect' [error] ./script/../config/../app/models/project.rb:323:in `notify' [error] ./script/../config/../app/models/project.rb:213:in `build_if_necessary' [error] ./script/../config/../app/models/polling_scheduler.rb:13:in `run' [error] ./script/builder:79 [error] ./script/builder:78:in `catch' [error] ./script/builder:78 [error] script/../config/../cruise:14:in `load' [error] script/../config/../cruise:14:in `builder' [error] script/../config/../cruise:68:in `send' [error] script/../config/../cruise:68 [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' [error] script/../config/../cruise:67 [error] Input/output error [error] ./script/../config/../lib/cruise_control/log.rb:35:in `write' [error] ./script/../config/../lib/cruise_control/log.rb:35:in `puts' [error] ./script/../config/../lib/cruise_control/log.rb:35:in `method_missing' [error] ./script/../config/../app/models/project.rb:327:in `notify' [error] ./script/../config/../app/models/project.rb:323:in `collect' [error] ./script/../config/../app/models/project.rb:323:in `notify' [error] ./script/../config/../app/models/project.rb:208:in `build_if_necessary' [error] ./script/../config/../app/models/polling_scheduler.rb:13:in `run' [error] ./script/builder:79 [error] ./script/builder:78:in `catch' [error] ./script/builder:78 [error] script/../config/../cruise:14:in `load' [error] script/../config/../cruise:14:in `builder' [error] script/../config/../cruise:68:in `send' [error] script/../config/../cruise:68 [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' [error] script/../config/../cruise:67 [fatal] Input/output error [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in `write' [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in `puts' [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in `log_error' [fatal] ./script/../config/../app/models/polling_scheduler.rb:17:in `run' [fatal] ./script/builder:79 [fatal] ./script/builder:78:in `catch' [fatal] ./script/builder:78 [fatal] script/../config/../cruise:14:in `load' [fatal] script/../config/../cruise:14:in `builder' [fatal] script/../config/../cruise:68:in `send' [fatal] script/../config/../cruise:68 [fatal] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' [fatal] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' [fatal] script/../config/../cruise:67 [info] [2008-03-31 10:59:48] Builder for project 'noaama_trunk' exited It appears that CruiseControl always wants a console to write to. I thought this was because of WEBRICK so I forced it to start in Daemon mode. Unfortunately that did not work and I am now at a loss. Is there something special I need to do to get CruiseControl to build projects in the background, so I can start it up as a service and let it do its work? I am running CentOS 5 and Ruby 1.8.6. Any insight would be greatly appreciated. Billy -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From thewoolleyman at gmail.com Mon Mar 31 14:46:08 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Mon, 31 Mar 2008 11:46:08 -0700 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? In-Reply-To: References: Message-ID: I think there is an example init script in the source somewhere. Also, I think I posted some improvements on it to the mailing list a few months back (but I think I was bad and didn't submit a patch). Anyway, the init script approach works fine for me. Let me know if you can't find them. On Mon, Mar 31, 2008 at 11:07 AM, Billy Kimble wrote: > Guys, > > I recently installed CruiseControl and I love it. So much that I want > to run it on its own server to handle all of my building needs. I > installed it, added projects, ran it, and everything was groovy. I > decided to stick the process in the background via: > > ./cruise start & > > And it put it in the background just fine too. Everything was kosher > until I tried logging out of my server. CruiseControl seemed to not > want to relinquish control of my SSH connection. I thought perhaps it > was a fluke on my connection so I just forcefully disconnected and > tried triggering CC to build, which failed with the following message: > > [error] Input/output error > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:20:in `write' > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:20:in `puts' > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:20:in `new_revisions_detected' > [error] ./script/../config/../app/models/project.rb:325:in `send' > [error] ./script/../config/../app/models/project.rb:325:in `notify' > [error] ./script/../config/../app/models/project.rb:323:in `collect' > [error] ./script/../config/../app/models/project.rb:323:in `notify' > [error] ./script/../config/../app/models/project.rb:208:in > `build_if_necessary' > [error] ./script/../config/../app/models/polling_scheduler.rb:13:in > `run' > [error] ./script/builder:79 > [error] ./script/builder:78:in `catch' > [error] ./script/builder:78 > [error] script/../config/../cruise:14:in `load' > [error] script/../config/../cruise:14:in `builder' > [error] script/../config/../cruise:68:in `send' > [error] script/../config/../cruise:68 > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' > [error] script/../config/../cruise:67 > [error] Input/output error > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:24:in `write' > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:24:in `puts' > [error] ./script/../config/../builder_plugins/installed/ > minimal_console_logger.rb:24:in `build_loop_failed' > [error] ./script/../config/../app/models/project.rb:325:in `send' > [error] ./script/../config/../app/models/project.rb:325:in `notify' > [error] ./script/../config/../app/models/project.rb:323:in `collect' > [error] ./script/../config/../app/models/project.rb:323:in `notify' > [error] ./script/../config/../app/models/project.rb:213:in > `build_if_necessary' > [error] ./script/../config/../app/models/polling_scheduler.rb:13:in > `run' > [error] ./script/builder:79 > [error] ./script/builder:78:in `catch' > [error] ./script/builder:78 > [error] script/../config/../cruise:14:in `load' > [error] script/../config/../cruise:14:in `builder' > [error] script/../config/../cruise:68:in `send' > [error] script/../config/../cruise:68 > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' > [error] script/../config/../cruise:67 > [error] Input/output error > [error] ./script/../config/../lib/cruise_control/log.rb:35:in `write' > [error] ./script/../config/../lib/cruise_control/log.rb:35:in `puts' > [error] ./script/../config/../lib/cruise_control/log.rb:35:in > `method_missing' > [error] ./script/../config/../app/models/project.rb:327:in `notify' > [error] ./script/../config/../app/models/project.rb:323:in `collect' > [error] ./script/../config/../app/models/project.rb:323:in `notify' > [error] ./script/../config/../app/models/project.rb:208:in > `build_if_necessary' > [error] ./script/../config/../app/models/polling_scheduler.rb:13:in > `run' > [error] ./script/builder:79 > [error] ./script/builder:78:in `catch' > [error] ./script/builder:78 > [error] script/../config/../cruise:14:in `load' > [error] script/../config/../cruise:14:in `builder' > [error] script/../config/../cruise:68:in `send' > [error] script/../config/../cruise:68 > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' > [error] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' > [error] script/../config/../cruise:67 > [fatal] Input/output error > [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in > `write' > [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in > `puts' > [fatal] ./script/../config/../app/models/polling_scheduler.rb:62:in > `log_error' > [fatal] ./script/../config/../app/models/polling_scheduler.rb:17:in > `run' > [fatal] ./script/builder:79 > [fatal] ./script/builder:78:in `catch' > [fatal] ./script/builder:78 > [fatal] script/../config/../cruise:14:in `load' > [fatal] script/../config/../cruise:14:in `builder' > [fatal] script/../config/../cruise:68:in `send' > [fatal] script/../config/../cruise:68 > [fatal] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' > [fatal] /usr/local/lib/ruby/1.8/fileutils.rb:121:in `cd' > [fatal] script/../config/../cruise:67 > [info] [2008-03-31 10:59:48] Builder for project 'noaama_trunk' exited > > It appears that CruiseControl always wants a console to write to. I > thought this was because of WEBRICK so I forced it to start in Daemon > mode. Unfortunately that did not work and I am now at a loss. Is > there something special I need to do to get CruiseControl to build > projects in the background, so I can start it up as a service and let > it do its work? I am running CentOS 5 and Ruby 1.8.6. Any insight > would be greatly appreciated. > > Billy > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > From nathen at visualcv.com Mon Mar 31 14:30:25 2008 From: nathen at visualcv.com (Nathen Harvey) Date: Mon, 31 Mar 2008 14:30:25 -0400 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? Message-ID: <47F12DC1.2090608@visualcv.com> Try this: ./cruise start --daemon For more info: ./cruise help start -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080331/937b8875/attachment.html From itsdave101 at gmail.com Mon Mar 31 15:09:16 2008 From: itsdave101 at gmail.com (David Meiners) Date: Mon, 31 Mar 2008 12:09:16 -0700 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? In-Reply-To: References: Message-ID: <47F136DC.3050607@gmail.com> here is a copy of my init script, i think i got it from a sample dir somewhere. #!/usr/bin/env ruby # # chkconfig: 345 94 16 # description: Startup script for CruiseControl.rb # in order to make cruise run as daemon, you need: # 1. cp $CCRB_HOME/daemon/cruise.sample $CCRB_HOME/daemon/cruise # 2. specify your cruise_path to $CCRB_HOME in $CCRB_HOME/daemon/cruise file # 3. ln -s $CCRB_HOME/daemon/cruise /etc/init.d/cruise (you may need to 'sudo' this) # 4. update-rc.d cruise (you may want to choose options by yourself, and you may need to 'sudo' this) # 5. it's done :> require "fileutils" include FileUtils require "rubygems" begin gem 'mongrel' rescue => e puts "Error: daemon mode of CC.rb requires mongrel installed" exit 1 end def cruise_path "/var/www/apps/cruisecontrol" end command = ARGV.shift case command when 'start' cd cruise_path system "/bin/su -c '/var/www/apps/cruisecontrol/cruise start -d' - deploy" exit 0 when 'stop' system "mongrel_rails stop -P #{cruise_path}/tmp/pids/mongrel.pid" Dir["#{cruise_path}/tmp/pids/builders/*.pid"].each do |pid_file| pid = File.open(pid_file){|f| f.read } system "kill -9 #{pid}" rm pid_file end exit 0 else p "Usage: /etc/init.d/cruise start|stop" exit 1 end From bkimble at inc21.com Mon Mar 31 15:47:38 2008 From: bkimble at inc21.com (Billy Kimble) Date: Mon, 31 Mar 2008 12:47:38 -0700 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? In-Reply-To: <47F12DC1.2090608@visualcv.com> References: <47F12DC1.2090608@visualcv.com> Message-ID: <71246059-40D4-4A1E-87D9-20D6AFE6F7BC@inc21.com> Sorry, I forgot to mention that I did try that. It produces the same connection usurping that has been plaguing me. I tried installing CC on my OSX desktop and it seems to work fine when I start it up in daemon mode. I can safely log out of my terminal connection and CruiseControl goes about its merry way. I am beginning to think this is a server problem. Has anyone run in to trouble using CruiseControl on CentOS 5 ? I am going to try the init script that Nathen and David mentioned / posted to see if running it as a service fixing my problems. This is driving me bonkers! Billy On Mar 31, 2008, at 11:30 AM, Nathen Harvey wrote: > Try this: > > ./cruise start --daemon > > For more info: > ./cruise help start > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080331/73856574/attachment.html From bkimble at inc21.com Mon Mar 31 15:59:48 2008 From: bkimble at inc21.com (Billy Kimble) Date: Mon, 31 Mar 2008 12:59:48 -0700 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? In-Reply-To: <71246059-40D4-4A1E-87D9-20D6AFE6F7BC@inc21.com> References: <47F12DC1.2090608@visualcv.com> <71246059-40D4-4A1E-87D9-20D6AFE6F7BC@inc21.com> Message-ID: <978ACD06-DC53-4EC4-9D67-BB0E0A8C56A6@inc21.com> Ok, so I Got it working! One glaring difference (that I overlooked) between my workstation and my current build server is that I do not have Mongrel installed on my server. One I did installed Mongrel, everything was working perfectly. The CruiseControl documentation does not mention the Mongrel requirement. Luckily you guys passed the /daemon/cruise.sample file here which had the following comment in it: puts "Error: daemon mode of CC.rb requires mongrel installed" This lead to me installing Mongrel to use the --daemon option. Perhaps a check could be put in to check for mongrel and complain if it is not present when someone starts in --daemon mode .. or at the very least state this in the 'help start' text :) Thanks guys. I'm cruising now! Billy On Mar 31, 2008, at 12:47 PM, Billy Kimble wrote: > Sorry, I forgot to mention that I did try that. It produces the > same connection usurping that has been plaguing me. > > I tried installing CC on my OSX desktop and it seems to work fine > when I start it up in daemon mode. I can safely log out of my > terminal connection and CruiseControl goes about its merry way. I > am beginning to think this is a server problem. Has anyone run in > to trouble using CruiseControl on CentOS 5 ? I am going to try the > init script that Nathen and David mentioned / posted to see if > running it as a service fixing my problems. This is driving me > bonkers! > > Billy > > On Mar 31, 2008, at 11:30 AM, Nathen Harvey wrote: > >> Try this: >> >> ./cruise start --daemon >> >> For more info: >> ./cruise help start >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080331/bd436633/attachment.html From jeremystellsmith at gmail.com Mon Mar 31 16:27:13 2008 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Mon, 31 Mar 2008 14:27:13 -0600 Subject: [Cruisecontrolrb-users] cruisecontrol.rb with C++ projects In-Reply-To: <1206946657.5890.29.camel@dp23406> References: <1206946657.5890.29.camel@dp23406> Message-ID: cc.rb will work with anything that you can kick off from command line and will return a non-zero status code iff it fails. so, to configure this, your cruise_config.rb file (either on the server or in your project's root directory) should look something like this : Project.configure do |project| project.build_command = "COMMAND" ... end where instead of command you put the command to build your project Jeremy On Mon, Mar 31, 2008 at 12:57 AM, Jonathan Naor wrote: > Hi, > > This has probably been asked a hundred times, but I couldn't find the > answer: how do I configure cruisecontrol.rb to build a c/c++ makefile? > > Thanks ** > *This e-mail message has been sent by Elbit Systems Ltd. * > *and is for the use of the intended recipients only. > The message may contain privileged or commercially sensitive information . > If you are not the intended recipient you are hereby notified that any > use, > distribution or copying of this communication is strictly prohibited, > and you are requested to delete the e-mail and any attachments* > *and notify the sender immediately.* > > _______________________________________________ > 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/20080331/6940a982/attachment-0001.html From averkhov at thoughtworks.com Mon Mar 31 16:54:57 2008 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 31 Mar 2008 15:54:57 -0500 Subject: [Cruisecontrolrb-users] CruiseControl in Daemon mode? In-Reply-To: <978ACD06-DC53-4EC4-9D67-BB0E0A8C56A6@inc21.com> Message-ID: > The CruiseControl documentation does not mention the Mongrel > requirement. Oops. Thanks for the heads up. As for CentOS 5, for some irrelevant historical reasons, that's my favorite server Linux. http://cruisecontrolrb.thoughtworks.com runs quite merrily on it. -- Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080331/aac1be2e/attachment.html