From averkhov at thoughtworks.com Tue Apr 3 11:42:09 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Tue, 3 Apr 2007 09:42:09 -0600 Subject: [Cruisecontrolrb-users] [ANN] CruiseControl.rb 1.1 Message-ID: Dear all, CruiseControl.rb 1.1 is out of the gates. CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] is a continuous integration tool. Its basic purpose in life is to alert members of a software project when one of them checks something into source control that breaks the build. Version 1.1 is a follow-up release to 1.0, mostly consisting of bug fixes and usability enhancements. Growl notification plugin, RSS feeds for individual projects, an ability to run as a proper Linux daemon and to peacefully coexist with non-English Subversion installs are the most noteworthy features of this release. List of changes in version ---------------- - individual RSS feeds for each project - documented options configurable through config/site_config.rb - added a "from" option to EmailNotifier configuration - added Growl notifier to available plugins - email notices can contain either full build log, or a link to the dashboard - builder does not clear RAILS_ENV environment variable before calling custom tasks - builder always sets RAILS_ENV environment to 'test' before calling default tasks - "cannot connect to Subversion" situations, plugin errors and other problems that occur outside of a build loop are now displayed on the dashboard - custom project settings are displayed on the build log page - [bugfix] Fixed cruise start --daemon option - [bugfix] Removed incomplete builds from RSS feeds - [bugfix] CC.rb can now live with localized (non-English) Subversion - [bugfix] Fixed problems with CCTray introduced in 1.0 by adding a new build status 'incomplete' - [bugfix] Corrected documentation to say "[cruise]/projects/" instead of "[cruise]/builds/" - [bugfix] Recognize Solaris as a platform Upgrading from 1.0 ---------------- There are no changes in data storage format, so upgrading from version 1.0 is easy: 1. Rename the old installation: mv ccrb/ ccrb.bak/ 2. Download from http://rubyforge.org/frs/?group_id=2918 and unpack. 3. Move to the path where the old installation was: mv cruisecontrolrb-1.1.0/ ccrb/ 4. Move projects/ directory: mv ccrb.bak/projects ccrb/ 5. Copy site_config.rb over: cp ccrb.bak/config/site_config.rb ccrb/config -- CruiseControl.rb team ThoughtWorks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070403/f9a16380/attachment.html From levent at leventali.com Wed Apr 4 10:06:02 2007 From: levent at leventali.com (Levent Ali) Date: Wed, 4 Apr 2007 15:06:02 +0100 Subject: [Cruisecontrolrb-users] Reporting as fixed even though there are test failures Message-ID: <76685bc50704040706s2532bb3cg42f042cce03d1fcc@mail.gmail.com> Even though there are errors and failures in our tests Cruise Control is reporting the build is NOT broken and thus not emailing anybody... aspire_rails_12x build 1818 finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds Build Changeset Revision 1818 committed by katem on 2007-04-04 12:47:28 removed breakpoint M /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb Test Failures and Errors Name: test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) Type: Failure Message: <1> expected but was <2>. ./test/unit/question_set_element_test.rb:328 Name: test_new_step_must_have_site_id(RegistrationWizardStepTest) Type: Failure Message: <1> expected but was <2>. ./test/unit/registration_wizard_step_test.rb:31 Name: test_run(TalentPoolNotificationsTest) Type: Failure Message: <3> expected but was <0>. ./test/unit/talent_pool_notifications_test.rb:60 Any ideas why this may be? cheers Levent From jeremystellsmith at gmail.com Wed Apr 4 11:39:29 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Wed, 4 Apr 2007 08:39:29 -0700 Subject: [Cruisecontrolrb-users] Reporting as fixed even though there are test failures In-Reply-To: <76685bc50704040706s2532bb3cg42f042cce03d1fcc@mail.gmail.com> References: <76685bc50704040706s2532bb3cg42f042cce03d1fcc@mail.gmail.com> Message-ID: Are you using Ruby 1.8.6? There is a bug with Ruby 1.8.6 that is causing Test::Unit to return the incorrect exit code, and cruise not to fail. For now, the fix is to go back to Ruby 1.8.4 or 1.8.5. We're working on a better workaround. On 4/4/07, Levent Ali wrote: > > Even though there are errors and failures in our tests Cruise Control > is reporting the build is NOT broken and thus not emailing anybody... > > aspire_rails_12x build 1818 > finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds > > Build Changeset > Revision 1818 committed by katem on 2007-04-04 12:47:28 removed > breakpoint M > /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb > Test Failures and Errors > Name: > test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) > Type: Failure Message: <1> expected but was <2>. > ./test/unit/question_set_element_test.rb:328 Name: > test_new_step_must_have_site_id(RegistrationWizardStepTest) Type: > Failure Message: <1> expected but was <2>. > ./test/unit/registration_wizard_step_test.rb:31 Name: > test_run(TalentPoolNotificationsTest) Type: Failure Message: <3> > expected but was <0>. ./test/unit/talent_pool_notifications_test.rb:60 > > > Any ideas why this may be? > > cheers > Levent > _______________________________________________ > 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/20070404/bfdc50cc/attachment.html From levent at leventali.com Wed Apr 4 11:42:26 2007 From: levent at leventali.com (Levent Ali) Date: Wed, 4 Apr 2007 16:42:26 +0100 Subject: [Cruisecontrolrb-users] Reporting as fixed even though there are test failures In-Reply-To: References: <76685bc50704040706s2532bb3cg42f042cce03d1fcc@mail.gmail.com> Message-ID: <76685bc50704040842s5b662258ldc68c79997103527@mail.gmail.com> Cheers, Alex Verkhovsky mentioned this as well... I am just trying it now with ruby 1.8.5 (full rake takes about 45 minutes)... we were running 1.8.6 on the ci server... Thanks again Levent On 4/4/07, Jeremy Stell-Smith wrote: > Are you using Ruby 1.8.6? There is a bug with Ruby 1.8.6 that is causing > Test::Unit to return the incorrect exit code, and cruise not to fail. For > now, the fix is to go back to Ruby 1.8.4 or 1.8.5. We're working on a > better workaround. > > On 4/4/07, Levent Ali wrote: > > > > Even though there are errors and failures in our tests Cruise Control > > is reporting the build is NOT broken and thus not emailing anybody... > > > > aspire_rails_12x build 1818 > > finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds > > > > Build Changeset > > Revision 1818 committed by katem on 2007-04-04 12:47:28 removed > > breakpoint M > /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb > > Test Failures and Errors > > Name: > test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) > > Type: Failure Message: <1> expected but was <2>. > > ./test/unit/question_set_element_test.rb:328 Name: > > > test_new_step_must_have_site_id(RegistrationWizardStepTest) > Type: > > Failure Message: <1> expected but was <2>. > > ./test/unit/registration_wizard_step_test.rb:31 Name: > > test_run(TalentPoolNotificationsTest) Type: Failure > Message: <3> > > expected but was <0>. > ./test/unit/talent_pool_notifications_test.rb:60 > > > > > > Any ideas why this may be? > > > > cheers > > Levent > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > Cruisecontrolrb-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > From an.olive.tree at gmail.com Thu Apr 5 09:34:17 2007 From: an.olive.tree at gmail.com (Hiroshi SAKURAI) Date: Thu, 5 Apr 2007 22:34:17 +0900 Subject: [Cruisecontrolrb-users] cc on NetBSD Message-ID: <6245f7a30704050634u75227b88p8f77bd0eaa7fa59@mail.gmail.com> Hi, CC works on NetBSD with following patch. Will you add that line in next release? thanks. Index: platform.rb =================================================================== --- platform.rb (revision 445) +++ platform.rb (working copy) @@ -11,6 +11,7 @@ when /freebsd/ then 'freebsd' when /linux/ then 'linux' when /solaris/ then 'solaris' + when /netbsd/ then 'netbsd' else raise "Unknown OS: #{target_os}" end end -- Hiroshi SAKURAI http://vimrc.hp.infoseek.co.jp/ From an.olive.tree at gmail.com Thu Apr 5 09:43:14 2007 From: an.olive.tree at gmail.com (Hiroshi SAKURAI) Date: Thu, 5 Apr 2007 22:43:14 +0900 Subject: [Cruisecontrolrb-users] error building project with no commit Message-ID: <6245f7a30704050643y76882c2aj604edf311c4e189e@mail.gmail.com> Hi, When I try to build a project that has no commit, I get following error. [error] undefined method `number' for nil:NilClass [error] undefined method `number' for nil:NilClass Build loop failed RuntimeError: Errors in plugins: ProjectLogger: undefined method `number' for nil:NilClass MinimalConsoleLogger: undefined method `number' for nil:NilClass ./script/../config/../script/../config/../app/models/project.rb:318:in `notify' ./script/../config/../script/../config/../app/models/project.rb:204:in `build_if_necessary' ./script/../config/../script/../config/../app/models/polling_scheduler.rb:13:in `run' ./script/../config/../script/builder:82 ./script/../config/../script/builder:81 script/../config/../cruise:14:in `builder' script/../config/../cruise:66 After I commit revision 1, CC works and emits no error. New revision 1 detected Build 1 started Build 1 FAILED I think it'd be better CC handles repository with no commit properly. Thanks. -- Hiroshi SAKURAI http://vimrc.hp.infoseek.co.jp/ From gigix1980 at gmail.com Fri Apr 6 11:30:38 2007 From: gigix1980 at gmail.com (Jeff Xiong) Date: Fri, 6 Apr 2007 23:30:38 +0800 Subject: [Cruisecontrolrb-users] cc on NetBSD In-Reply-To: <6245f7a30704050634u75227b88p8f77bd0eaa7fa59@mail.gmail.com> References: <6245f7a30704050634u75227b88p8f77bd0eaa7fa59@mail.gmail.com> Message-ID: <20fd9dc50704060830k68ed2785p2a00546fb8cc41c1@mail.gmail.com> Can we do following? when /bsd/ then 'bsd' I haven't checked code yet, just an idea. On 4/5/07, Hiroshi SAKURAI wrote: > Hi, > > CC works on NetBSD with following patch. > Will you add that line in next release? > > thanks. > > Index: platform.rb > =================================================================== > --- platform.rb (revision 445) > +++ platform.rb (working copy) > @@ -11,6 +11,7 @@ > when /freebsd/ then 'freebsd' > when /linux/ then 'linux' > when /solaris/ then 'solaris' > + when /netbsd/ then 'netbsd' > else raise "Unknown OS: #{target_os}" > end > end > > > -- > Hiroshi SAKURAI > http://vimrc.hp.infoseek.co.jp/ > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- Jeff Xiong Editor of InfoQ China: http://www.infoq.com/cn/ Contributor of CruiseControl.rb: http://cruisecontrolrb.thoughtworks.com/ From gedanken at io.com Fri Apr 6 14:27:58 2007 From: gedanken at io.com (Gedanken) Date: Fri, 6 Apr 2007 13:27:58 -0500 (CDT) Subject: [Cruisecontrolrb-users] Automation? tags? Message-ID: <20070406130738.H58231@eris.io.com> Warning - Im brand new to CruiseControl, and CruiseControl.rb. i tink half the stuff I learned about CC is actualyl now wrong when I am using cc.rb =) I am slightly familiar with Capistrano, having installed it and used it once. We have cc.rb up and running and doing its thing - making builds from svn changes. Step 2 has fallen to me and I am doing the research necessary to get the task finished. Any advice, guidance, or links you guys can provide would be appreciated! Apologies in advance for being such a squid. What I want to do is: - Have an automated way of triggering a build. - have this process be able to either build the current HEAD or a few pre-defined tags such as DEMO, BOBS_TAG, etc. It does *not* have to be able to build any arbitrary tag that is in svn, just a couple we hard code at the start. I was thinkign there would be an easy way to write a web page with a few shiny red buttons like 'Build HEAD now' and 'Build DEMO now' etc and interface with JMX server that i found out about from googling, but i current believe that only would work (if at all) if we were using regualr cruisecontrol, not cruisecontrol.rb. For a variety of reasons i cant quite elucidate, we greatly prefer to use the cc.rb solution that you fine folks use/maintain/wax. Can someone point me in the right direction please? -- gedanken From PDJulius at ThoughtWorks.COM Tue Apr 10 14:53:25 2007 From: PDJulius at ThoughtWorks.COM (Paul D Julius) Date: Tue, 10 Apr 2007 13:53:25 -0500 Subject: [Cruisecontrolrb-users] Invitation to CITCON North America Message-ID: Sorry if this is a repeat for some of you, but I never formally invited the Ruby continuous integrators. It would be great to get some representatives from the CC.rb community at CITCON. Continuous Integration and Testing Conference (CITCON) http://citconf.com/ The Open Information Foundation and the CITCON Organization Committee are proud to announce that registration is now open for our upcoming 2nd Annual North American event. CITCON Dallas/Ft. Worth 2007 is April 27 & 28th at the American Airlines Training & Conference Center in Fort Worth, Texas. As always, attendance costs nothing. Come prepared to share your ideas and be overwhelmed by everyone else's ideas. Register at the conference website: http://citconf.com/register.php The registration deadline is Friday, April 13, 2007 and limited to the first 100 registrants. As a special request, please forward this invitation on to anyone you think might be interested. Since our advertising budget is $0, we would really appreciate any help you can offer in getting the word out. If you are a blogger, please blog about CITCON -- before and after the conference. If you are speaking at other conferences, please put in a good word for us. If you are active on other mailing lists which are topic relevant, please post about CITCON. Etc. Sincerely, Paul Julius Co-chair, CITCON North America 2007 Co-founder, Open Information Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070410/de0af95a/attachment.html From alexey.verkhovsky at gmail.com Thu Apr 12 03:17:41 2007 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Thu, 12 Apr 2007 01:17:41 -0600 Subject: [Cruisecontrolrb-users] Plans for version 1.2 Message-ID: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> Hi all, Let's discuss future plans for CC.rb. Version 1.1 was about fixing bugs and inconveniences that users of 1.0 told us about. In version 1.2 we plan to mostly work on two things: build chaining and dashboard performance. And we'd like some feedback. Is there are another missing feature more important to you than these two, or perhaps important enough for the next version? Build chaining is telling one project that new builds should be triggered by a successful build of another project. This can be useful in a couple of scenarios, when splitting a build to fast and slow parts. or when you have multiple projects that depend on each other (e.g., two applications that depends on the same library). This was requested by several ThoughtWorks Ruby projects, so we are putting it in. As for dashboard performance, it's not terribly slow now (typical response time is around 100-300 msec), but if you accumulate a long history of builds (say, over a thousand), and connect many enough CCTrays / dashboards (all these things hit the server often), CC.rb will eventually grind to a halt. Workaround for now is to remove some old builds from [cruise]/projects/your_project/ directory. We are putting some optimisations in 1.2 that should make it unnecessary. By the way, anyone watching CC.rb trunk would notice that new development has slowed down. The team is doing some other stuff right now (watch Ruby-talk for further announcements etc), but we are still committed to maintaining this tool and resolving any problems you, our users, may have. Your comments, please. Best regards, Alexey Verkhovsky CC.rb team ThoughtWorks From holmberg at iar.se Thu Apr 12 05:58:25 2007 From: holmberg at iar.se (Johan Holmberg) Date: Thu, 12 Apr 2007 11:58:25 +0200 Subject: [Cruisecontrolrb-users] 1-1 project-archive mapping? Message-ID: <461E02C1.1000208@iar.se> Hi! If I have understood things correctly in CC.rb, there is a 1-1 mapping between "projects" and Subversion modules. For example the normal way to add a project is a command like: $ cruise add -u I'm not sure how to use CC.rb for my situation where I don't have such a direct mapping. I have several Subversion modules that I need to checkout to a sandbox-structure like: SOMEDIR/moduleA # from http://HOST/PATH1/moduleA/trunk SOMEDIR/moduleB # from http://HOST/PATH2/moduleB/trunk SOMEDIR/moduleC # from http://HOST/PATH3/moduleC/trunk My first thought was to create a special Subversion module "testABC" that just contained a "Rakefile" for CC.rb to use, and then the needed svn:externals to bring in moduleA, moduleB and moduleC as subdirectories. But I guess that will make it impossible for CC.rb to detect that something has happened in the Subversion archive. After initial setup the testABC module will never change. The changes will be in moduleA, moduleB and moduleC, hidden by the svn:external links. A build in CC.rb also seem to be identified with the revision number. In my scenario I have *three* different Subversion module, each with a "latest revision" of its own. I have tried to look for some configuration possibility to make my current scenario work. But I have not found out how to do. Is it possible? Or is there some other way to accomplish something similar? /Johan Holmberg From cch1 at hapgoods.com Thu Apr 12 07:57:58 2007 From: cch1 at hapgoods.com (Chris Hapgood) Date: Thu, 12 Apr 2007 07:57:58 -0400 Subject: [Cruisecontrolrb-users] Plans for version 1.2 In-Reply-To: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> References: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> Message-ID: <007501c77cf9$d0440c90$6601a8c0@hapgoods.com> MY WISH LIST: 1. I would be nice to have some more control over the cruise processes. There should be a stop option to the cruise command that stops all builders as well as the main Rails process. 2. Better documentation, with more examples. I've gotten over most of the learning hump, but for Those Who Come Late to the Party, good docs will help a lot. I'll throw some more in eventually. Chris Hapgood Phone: +1 434 989 8584 Skype: chris.hapgood Email: cch1 at hapgoods.com -----Original Message----- From: cruisecontrolrb-users-bounces at rubyforge.org [mailto:cruisecontrolrb-users-bounces at rubyforge.org] On Behalf Of Alexey Verkhovsky Sent: Thursday, April 12, 2007 03:18 To: cruisecontrolrb-users at rubyforge.org Subject: [Cruisecontrolrb-users] Plans for version 1.2 Hi all, Let's discuss future plans for CC.rb. Version 1.1 was about fixing bugs and inconveniences that users of 1.0 told us about. In version 1.2 we plan to mostly work on two things: build chaining and dashboard performance. And we'd like some feedback. Is there are another missing feature more important to you than these two, or perhaps important enough for the next version? Build chaining is telling one project that new builds should be triggered by a successful build of another project. This can be useful in a couple of scenarios, when splitting a build to fast and slow parts. or when you have multiple projects that depend on each other (e.g., two applications that depends on the same library). This was requested by several ThoughtWorks Ruby projects, so we are putting it in. As for dashboard performance, it's not terribly slow now (typical response time is around 100-300 msec), but if you accumulate a long history of builds (say, over a thousand), and connect many enough CCTrays / dashboards (all these things hit the server often), CC.rb will eventually grind to a halt. Workaround for now is to remove some old builds from [cruise]/projects/your_project/ directory. We are putting some optimisations in 1.2 that should make it unnecessary. By the way, anyone watching CC.rb trunk would notice that new development has slowed down. The team is doing some other stuff right now (watch Ruby-talk for further announcements etc), but we are still committed to maintaining this tool and resolving any problems you, our users, may have. Your comments, please. Best regards, Alexey Verkhovsky CC.rb team ThoughtWorks _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From mdeiters at msn.com Thu Apr 12 09:12:15 2007 From: mdeiters at msn.com (Matt Deiters) Date: Thu, 12 Apr 2007 08:12:15 -0500 Subject: [Cruisecontrolrb-users] Plans for version 1.2 In-Reply-To: <007501c77cf9$d0440c90$6601a8c0@hapgoods.com> Message-ID: I second Chris' recommendation: >1. I would be nice to have some more control over the cruise processes. >There should be a stop >option to the cruise command that stops all >builders as well as the main Rails process. Matt >From: "Chris Hapgood" >To: "'Alexey Verkhovsky'" >, >Subject: Re: [Cruisecontrolrb-users] Plans for version 1.2 >Date: Thu, 12 Apr 2007 07:57:58 -0400 > >MY WISH LIST: > >1. I would be nice to have some more control over the cruise processes. >There should be a stop option to the cruise command that stops all builders >as well as the main Rails process. > >2. Better documentation, with more examples. I've gotten over most of the >learning hump, but for Those Who Come Late to the Party, good docs will >help a lot. > >I'll throw some more in eventually. > >Chris Hapgood >Phone: +1 434 989 8584 >Skype: chris.hapgood >Email: cch1 at hapgoods.com > >-----Original Message----- >From: cruisecontrolrb-users-bounces at rubyforge.org >[mailto:cruisecontrolrb-users-bounces at rubyforge.org] On Behalf Of Alexey >Verkhovsky >Sent: Thursday, April 12, 2007 03:18 >To: cruisecontrolrb-users at rubyforge.org >Subject: [Cruisecontrolrb-users] Plans for version 1.2 > >Hi all, > >Let's discuss future plans for CC.rb. > >Version 1.1 was about fixing bugs and inconveniences that users of 1.0 >told us about. > >In version 1.2 we plan to mostly work on two things: build chaining >and dashboard performance. And we'd like some feedback. Is there are >another missing feature more important to you than these two, or >perhaps important enough for the next version? > >Build chaining is telling one project that new builds should be >triggered by a successful build of another project. This can be useful >in a couple of scenarios, when splitting a build to fast and slow >parts. or when you have multiple projects that depend on each other >(e.g., two applications that depends on the same library). This was >requested by several ThoughtWorks Ruby projects, so we are putting it >in. > >As for dashboard performance, it's not terribly slow now (typical >response time is around 100-300 msec), but if you accumulate a long >history of builds (say, over a thousand), and connect many enough >CCTrays / dashboards (all these things hit the server often), CC.rb >will eventually grind to a halt. Workaround for now is to remove some >old builds from [cruise]/projects/your_project/ directory. We are >putting some optimisations in 1.2 that should make it unnecessary. > >By the way, anyone watching CC.rb trunk would notice that new >development has slowed down. The team is doing some other stuff right >now (watch Ruby-talk for further announcements etc), but we are still >committed to maintaining this tool and resolving any problems you, our >users, may have. > >Your comments, please. > >Best regards, >Alexey Verkhovsky >CC.rb team >ThoughtWorks >_______________________________________________ >Cruisecontrolrb-users mailing list >Cruisecontrolrb-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > >_______________________________________________ >Cruisecontrolrb-users mailing list >Cruisecontrolrb-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From averkhov at thoughtworks.com Thu Apr 12 11:06:56 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 12 Apr 2007 10:06:56 -0500 Subject: [Cruisecontrolrb-users] 1-1 project-archive mapping? In-Reply-To: <461E02C1.1000208@iar.se> Message-ID: cruisecontrolrb-users-bounces at rubyforge.org wrote on 04/12/2007 03:58:25 AM: > I have tried to look for some configuration possibility to make my > current scenario work. But I have not found out how to do. That's exactly where build chaining (discussed in yesterday "Plans for version 1.2" post) comes handy. In the absense of it, you can actually hack something together, as follows: 1. Set a project for each of the three modules. 2. Create a project for the sandbox. Make it watch an SVN path with its own build file and cruise_config.rb, even if you have no other sources for it. 3. In each of the module builds make "touch [cruise]/projects/sandbox/build_requested" the last step. -- Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070412/c31ed95f/attachment.html From gedanken at io.com Thu Apr 12 12:49:18 2007 From: gedanken at io.com (Gedanken) Date: Thu, 12 Apr 2007 11:49:18 -0500 (CDT) Subject: [Cruisecontrolrb-users] Deploying after a build In-Reply-To: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> References: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> Message-ID: <20070412114205.B54711@eris.io.com> What are some of the better ways to deploy the code into a web environment after building with cruisecontrol.rb? I am still new to a lot of this and I really am not sure my questions make a ton of sense, or if i fully understand all that CruiseControl can do. What I have done so far is: (with Alexey's kind help!) - create a tag of a project in svn - create a new cruisecontrol.rb project for that tag - use a cron job to do a nightly build just of that tag using 'touch' Now what I want to do is: - If the build was successful, deploy it to /var/www/ What I am currently trying to implement is: - modify cruise_config.rb to use "./build_my_app.sh" (i needed a ./ ) - run 'rake' - run a capistrano command, assuming rake succeeded Is this a clueless noob fumbling down the wrong path or am I actually going to get somewhere? Im especially not sure how to write the script to test for success of the rake build. Matt -- gedanken From tdjordan at gmail.com Fri Apr 13 12:18:00 2007 From: tdjordan at gmail.com (Tom Jordan) Date: Fri, 13 Apr 2007 11:18:00 -0500 Subject: [Cruisecontrolrb-users] Plans for version 1.2 In-Reply-To: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> References: <3945c4270704120017i456faf27p1a5e68929a450697@mail.gmail.com> Message-ID: <4ebb98050704130918h5c02a854g1a22d7de90293897@mail.gmail.com> Here are some: 1. I am now managing multiple projects across multiple platforms and build machines. What I would like is a simple way to have the build machines be build agents and have one federated dashboard for the build farm. Any ideas? (maybe a leverage drb protocol passing yaml encoded triggers?) 2. As some projects use CC.NET and others CC.Java and now CC.rb, have CC.rb be able to federate the build results from CC.NET and CC.Java. Thanks for all you are doing, -- Tom. On 4/12/07, Alexey Verkhovsky wrote: > Hi all, > > Let's discuss future plans for CC.rb. > > Version 1.1 was about fixing bugs and inconveniences that users of 1.0 > told us about. > > In version 1.2 we plan to mostly work on two things: build chaining > and dashboard performance. And we'd like some feedback. Is there are > another missing feature more important to you than these two, or > perhaps important enough for the next version? > > Build chaining is telling one project that new builds should be > triggered by a successful build of another project. This can be useful > in a couple of scenarios, when splitting a build to fast and slow > parts. or when you have multiple projects that depend on each other > (e.g., two applications that depends on the same library). This was > requested by several ThoughtWorks Ruby projects, so we are putting it > in. > > As for dashboard performance, it's not terribly slow now (typical > response time is around 100-300 msec), but if you accumulate a long > history of builds (say, over a thousand), and connect many enough > CCTrays / dashboards (all these things hit the server often), CC.rb > will eventually grind to a halt. Workaround for now is to remove some > old builds from [cruise]/projects/your_project/ directory. We are > putting some optimisations in 1.2 that should make it unnecessary. > > By the way, anyone watching CC.rb trunk would notice that new > development has slowed down. The team is doing some other stuff right > now (watch Ruby-talk for further announcements etc), but we are still > committed to maintaining this tool and resolving any problems you, our > users, may have. > > Your comments, please. > > Best regards, > Alexey Verkhovsky > CC.rb team > ThoughtWorks > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- "Nothing will ever be attempted, if all possible objections must first be overcome." - Samuel Johnson "Luck is what happens when preparation meets opportunity." - Seneca From marcus at marcuscrafter.com Mon Apr 16 22:21:04 2007 From: marcus at marcuscrafter.com (Marcus Crafter) Date: Tue, 17 Apr 2007 12:21:04 +1000 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? Message-ID: Hi All, Hope all is going well. Just installed CC.rb in my development environment here and it looks great. Top stuff. I was able to get my Rails project registered and building properly which was awesome. I'm using RSpec for my tests rather than Test::Unit, so I modified the project.rake_task to be 'spec' rather than commented out, however it seems that CC.rb now tries to run my spec's over the production database rather than the test database. Running a 'rake spec' from the command line with the same project works fine as expected, however unfortunately through CC.rb it fails. Anyone got any thoughts where things might be wrong with the configuration of what database to use? or any pointers where to take a look? Thanks for any thoughts, ideas. Cheers, Marcus From gigix1980 at gmail.com Mon Apr 16 22:43:52 2007 From: gigix1980 at gmail.com (Jeff Xiong) Date: Tue, 17 Apr 2007 10:43:52 +0800 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? In-Reply-To: <20fd9dc50704161943p6cac51ei2d03763cbd671c38@mail.gmail.com> References: <20fd9dc50704161943p6cac51ei2d03763cbd671c38@mail.gmail.com> Message-ID: <20fd9dc50704161943we59603blafa5f821d0731d2@mail.gmail.com> Have you tried to create a /lib/tasks/cruise.rake file, then invoke 'spec' task in it? desc 'Continuous build target' task :cruise do Rake::Task["speck"].invoke end CC.rb prefers 'cruise' rake task. On 4/17/07, Marcus Crafter wrote: > Hi All, > > Hope all is going well. > > Just installed CC.rb in my development environment here and it looks > great. Top stuff. > > I was able to get my Rails project registered and building properly > which was awesome. > > I'm using RSpec for my tests rather than Test::Unit, so I modified > the project.rake_task to be 'spec' rather than commented out, however > it seems that CC.rb now tries to run my spec's over the production > database rather than the test database. > > Running a 'rake spec' from the command line with the same project > works fine as expected, however unfortunately through CC.rb it fails. > > Anyone got any thoughts where things might be wrong with the > configuration of what database to use? or any pointers where to take > a look? > > Thanks for any thoughts, ideas. > > Cheers, > > Marcus > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- Jeff Xiong Software Journeyman - http://gigix.thoughtworkers.org Open Source Contributor - http://cruisecontrolrb.thoughtworks.com/ Technical Evangelist - http://www.infoq.com/cn/ From marcus at marcuscrafter.com Mon Apr 16 22:54:11 2007 From: marcus at marcuscrafter.com (Marcus Crafter) Date: Tue, 17 Apr 2007 12:54:11 +1000 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? In-Reply-To: <20fd9dc50704161943we59603blafa5f821d0731d2@mail.gmail.com> References: <20fd9dc50704161943p6cac51ei2d03763cbd671c38@mail.gmail.com> <20fd9dc50704161943we59603blafa5f821d0731d2@mail.gmail.com> Message-ID: <25F20148-7F98-4C0E-9A2D-A94FA1E849E9@marcuscrafter.com> Hi Jeff, Thanks for your response - just gave that a go, but unfortunately the same error occurs - it seems that it's able to run the spec's, just that they all fail due to the wrong database: 1) ActiveRecord::StatementInvalid in 'A new Activation object should be invalid without a name' Mysql::Error: Table 'cms_production.activations' doesn't exist: SHOW FIELDS FROM activations ./spec/models/activation_spec.rb:7: ...... I've checked my project all over, and there's no setting of the RAILS_ENV to production anywhere, and a rake spec on the command line works fine with the right database. Still digging in to it.. Cheers, Marcus On 17/04/2007, at 12:43 PM, Jeff Xiong wrote: > Have you tried to create a /lib/tasks/cruise.rake file, then invoke > 'spec' task in it? > > desc 'Continuous build target' > task :cruise do > Rake::Task["speck"].invoke > end > > CC.rb prefers 'cruise' rake task. > > On 4/17/07, Marcus Crafter wrote: >> Hi All, >> >> Hope all is going well. >> >> Just installed CC.rb in my development environment here and it looks >> great. Top stuff. >> >> I was able to get my Rails project registered and building properly >> which was awesome. >> >> I'm using RSpec for my tests rather than Test::Unit, so I modified >> the project.rake_task to be 'spec' rather than commented out, however >> it seems that CC.rb now tries to run my spec's over the production >> database rather than the test database. >> >> Running a 'rake spec' from the command line with the same project >> works fine as expected, however unfortunately through CC.rb it fails. >> >> Anyone got any thoughts where things might be wrong with the >> configuration of what database to use? or any pointers where to take >> a look? >> >> Thanks for any thoughts, ideas. >> >> Cheers, >> >> Marcus >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > > > -- > Jeff Xiong > Software Journeyman - http://gigix.thoughtworkers.org > Open Source Contributor - http://cruisecontrolrb.thoughtworks.com/ > Technical Evangelist - http://www.infoq.com/cn/ > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From averkhov at thoughtworks.com Mon Apr 16 23:00:21 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 16 Apr 2007 22:00:21 -0500 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? In-Reply-To: <25F20148-7F98-4C0E-9A2D-A94FA1E849E9@marcuscrafter.com> Message-ID: Marcus, CC.rb version 1.1 doesn't change RAILS_ENV, either (earlier versions did). If you want to try and force it to be 'test' before 'spec' task is invoked, try this: desc 'Continuous build target' task :cruise do ENV['RAILS_ENV'] = 'test' Rake::Task['spec'].invoke end If that doesn't help, please send me your Rakefile (or whatever needed to reproduce the issue) off-list, and I'll look into it. Best regards, Alex Marcus Crafter Sent by: cruisecontrolrb-users-bounces at rubyforge.org 04/16/2007 08:54 PM To cruisecontrolrb-users at rubyforge.org cc Subject Re: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? Hi Jeff, Thanks for your response - just gave that a go, but unfortunately the same error occurs - it seems that it's able to run the spec's, just that they all fail due to the wrong database: 1) ActiveRecord::StatementInvalid in 'A new Activation object should be invalid without a name' Mysql::Error: Table 'cms_production.activations' doesn't exist: SHOW FIELDS FROM activations ./spec/models/activation_spec.rb:7: ...... I've checked my project all over, and there's no setting of the RAILS_ENV to production anywhere, and a rake spec on the command line works fine with the right database. Still digging in to it.. Cheers, Marcus On 17/04/2007, at 12:43 PM, Jeff Xiong wrote: > Have you tried to create a /lib/tasks/cruise.rake file, then invoke > 'spec' task in it? > > desc 'Continuous build target' > task :cruise do > Rake::Task["speck"].invoke > end > > CC.rb prefers 'cruise' rake task. > > On 4/17/07, Marcus Crafter wrote: >> Hi All, >> >> Hope all is going well. >> >> Just installed CC.rb in my development environment here and it looks >> great. Top stuff. >> >> I was able to get my Rails project registered and building properly >> which was awesome. >> >> I'm using RSpec for my tests rather than Test::Unit, so I modified >> the project.rake_task to be 'spec' rather than commented out, however >> it seems that CC.rb now tries to run my spec's over the production >> database rather than the test database. >> >> Running a 'rake spec' from the command line with the same project >> works fine as expected, however unfortunately through CC.rb it fails. >> >> Anyone got any thoughts where things might be wrong with the >> configuration of what database to use? or any pointers where to take >> a look? >> >> Thanks for any thoughts, ideas. >> >> Cheers, >> >> Marcus >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > > > -- > Jeff Xiong > Software Journeyman - http://gigix.thoughtworkers.org > Open Source Contributor - http://cruisecontrolrb.thoughtworks.com/ > Technical Evangelist - http://www.infoq.com/cn/ > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070416/ef83f6d1/attachment.html From marcus at marcuscrafter.com Tue Apr 17 07:56:24 2007 From: marcus at marcuscrafter.com (Marcus Crafter) Date: Tue, 17 Apr 2007 21:56:24 +1000 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? In-Reply-To: References: Message-ID: <6431C857-389E-49A4-9444-36BC861C2DBC@marcuscrafter.com> Hi Alex, Thanks for your help - unfortunately setting the environment directly didn't fix it either - I'll follow through and send you a simple environment that reproduces the problem offline now. Cheers, Marcus On 17/04/2007, at 1:00 PM, Alexey Verkhovsky wrote: > > Marcus, > > CC.rb version 1.1 doesn't change RAILS_ENV, either (earlier > versions did). > > If you want to try and force it to be 'test' before 'spec' task is > invoked, try this: > > desc 'Continuous build target' > task :cruise do > ENV['RAILS_ENV'] = 'test' > Rake::Task['spec'].invoke > end > > If that doesn't help, please send me your Rakefile (or whatever > needed to reproduce the issue) off-list, and I'll look into it. > > Best regards, > Alex > > > > > Marcus Crafter > Sent by: cruisecontrolrb-users-bounces at rubyforge.org > 04/16/2007 08:54 PM > > To > cruisecontrolrb-users at rubyforge.org > cc > Subject > Re: [Cruisecontrolrb-users] CC.rb, rails and rspec tests > using production database? > > > > > > Hi Jeff, > > Thanks for your response - just gave that a go, but unfortunately the > same error occurs - it seems that it's able to run the spec's, just > that they all fail due to the wrong database: > > 1) ActiveRecord::StatementInvalid in 'A new Activation object should > be invalid without a name' Mysql::Error: Table > 'cms_production.activations' doesn't exist: SHOW FIELDS FROM > activations ./spec/models/activation_spec.rb:7: > ...... > > I've checked my project all over, and there's no setting of the > RAILS_ENV to production anywhere, and a rake spec on the command line > works fine with the right database. > > Still digging in to it.. > > Cheers, > > Marcus > > > On 17/04/2007, at 12:43 PM, Jeff Xiong wrote: > > > Have you tried to create a /lib/tasks/cruise.rake file, then invoke > > 'spec' task in it? > > > > desc 'Continuous build target' > > task :cruise do > > Rake::Task["speck"].invoke > > end > > > > CC.rb prefers 'cruise' rake task. > > > > On 4/17/07, Marcus Crafter wrote: > >> Hi All, > >> > >> Hope all is going well. > >> > >> Just installed CC.rb in my development environment here and it > looks > >> great. Top stuff. > >> > >> I was able to get my Rails project registered and building properly > >> which was awesome. > >> > >> I'm using RSpec for my tests rather than Test::Unit, so I modified > >> the project.rake_task to be 'spec' rather than commented out, > however > >> it seems that CC.rb now tries to run my spec's over the production > >> database rather than the test database. > >> > >> Running a 'rake spec' from the command line with the same project > >> works fine as expected, however unfortunately through CC.rb it > fails. > >> > >> Anyone got any thoughts where things might be wrong with the > >> configuration of what database to use? or any pointers where to > take > >> a look? > >> > >> Thanks for any thoughts, ideas. > >> > >> Cheers, > >> > >> Marcus > >> _______________________________________________ > >> Cruisecontrolrb-users mailing list > >> Cruisecontrolrb-users at rubyforge.org > >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > >> > > > > > > -- > > Jeff Xiong > > Software Journeyman - http://gigix.thoughtworkers.org > > Open Source Contributor - http://cruisecontrolrb.thoughtworks.com/ > > Technical Evangelist - http://www.infoq.com/cn/ > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > Cruisecontrolrb-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From jeem at hughesorama.com Tue Apr 17 09:23:50 2007 From: jeem at hughesorama.com (Jim Hughes) Date: Tue, 17 Apr 2007 08:23:50 -0500 Subject: [Cruisecontrolrb-users] CC.rb, rails and rspec tests using production database? In-Reply-To: <8807213B-B07C-4CFA-BA17-D58196E37E0C@marcuscrafter.com> References: <6431C857-389E-49A4-9444-36BC861C2DBC@marcuscrafter.com> <6166D070-9158-4E58-8653-F04571C557FE@hughesorama.com> <8807213B-B07C-4CFA-BA17-D58196E37E0C@marcuscrafter.com> Message-ID: db:test:clone really wants to use the test environment. (If you look at your test.log, you might notice that even when your specs are trying to run against production or development, your test db is being cloned correctly.) Since I am testing in a non-standard environment, cruise_build, I use db:migrate, which uses the current RAILS_ENV. J. On Apr 17, 2007, at 8:04 AM, Marcus Crafter wrote: > Hi Jim, > > Awesome, thanks for that mate, I'll take a closer look at that in > the morning when I can try it out. Looks like I might have to do > something similar to get it to work on my test database. > > BTW, something else I'm just wondering, since you're setting your > RAILS_ENV explicitly, do you prefer to use db:migrate to load up > your non-development databases such as test, rather than the > db:test:clone task? > > From what I can tell, db:test:clone doesn't include data from your > development database, it just loads up the schema - in my case I > have static data in a few tables that I had in migrations after the > create_table declarations - they don't show up at all in any non- > migrated database using clone, etc. > > Seems like db:test:clone isn't the right thing to use to create > your test database? Or have I lost the plot somewhere along the > track? :) > > Thanks again for your help. > > Cheers, > > Marcus > > On 17/04/2007, at 10:32 PM, Jim Hughes wrote: > >> Here's a snippet from my rakefile: >> >> task :build_env do >> ENV['RAILS_ENV'] = 'cruise_build' >> RAILS_ENV = 'cruise_build' >> end >> >> task :cruise => [:build_env,'db:migrate',:spec_cruise] >> >> I found setting RAILS_ENV to be necessary. (I use a different env >> from test because the db is different on my ci server.) >> >> Jim >> >> >> On Apr 17, 2007, at 6:56 AM, Marcus Crafter wrote: >> >>> Hi Alex, >>> >>> Thanks for your help - unfortunately setting the environment >>> directly >>> didn't fix it either - I'll follow through and send you a simple >>> environment that reproduces the problem offline now. >>> >>> Cheers, >>> >>> Marcus >>> >>> >>> On 17/04/2007, at 1:00 PM, Alexey Verkhovsky wrote: >>> >>>> >>>> Marcus, >>>> >>>> CC.rb version 1.1 doesn't change RAILS_ENV, either (earlier >>>> versions did). >>>> >>>> If you want to try and force it to be 'test' before 'spec' task is >>>> invoked, try this: >>>> >>>> desc 'Continuous build target' >>>> task :cruise do >>>> ENV['RAILS_ENV'] = 'test' >>>> Rake::Task['spec'].invoke >>>> end >>>> >>>> If that doesn't help, please send me your Rakefile (or whatever >>>> needed to reproduce the issue) off-list, and I'll look into it. >>>> >>>> Best regards, >>>> Alex >>>> >>>> >>>> >>>> >>>> Marcus Crafter >>>> Sent by: cruisecontrolrb-users-bounces at rubyforge.org >>>> 04/16/2007 08:54 PM >>>> >>>> To >>>> cruisecontrolrb-users at rubyforge.org >>>> cc >>>> Subject >>>> Re: [Cruisecontrolrb-users] CC.rb, rails and rspec tests >>>> using production database? >>>> >>>> >>>> >>>> >>>> >>>> Hi Jeff, >>>> >>>> Thanks for your response - just gave that a go, but >>>> unfortunately the >>>> same error occurs - it seems that it's able to run the spec's, just >>>> that they all fail due to the wrong database: >>>> >>>> 1) ActiveRecord::StatementInvalid in 'A new Activation object >>>> should >>>> be invalid without a name' Mysql::Error: Table >>>> 'cms_production.activations' doesn't exist: SHOW FIELDS FROM >>>> activations ./spec/models/activation_spec.rb:7: >>>> ...... >>>> >>>> I've checked my project all over, and there's no setting of the >>>> RAILS_ENV to production anywhere, and a rake spec on the command >>>> line >>>> works fine with the right database. >>>> >>>> Still digging in to it.. >>>> >>>> Cheers, >>>> >>>> Marcus >>>> >>>> >>>> On 17/04/2007, at 12:43 PM, Jeff Xiong wrote: >>>> >>>>> Have you tried to create a /lib/tasks/cruise.rake file, then >>>>> invoke >>>>> 'spec' task in it? >>>>> >>>>> desc 'Continuous build target' >>>>> task :cruise do >>>>> Rake::Task["speck"].invoke >>>>> end >>>>> >>>>> CC.rb prefers 'cruise' rake task. >>>>> >>>>> On 4/17/07, Marcus Crafter wrote: >>>>>> Hi All, >>>>>> >>>>>> Hope all is going well. >>>>>> >>>>>> Just installed CC.rb in my development environment here and it >>>> looks >>>>>> great. Top stuff. >>>>>> >>>>>> I was able to get my Rails project registered and building >>>>>> properly >>>>>> which was awesome. >>>>>> >>>>>> I'm using RSpec for my tests rather than Test::Unit, so I >>>>>> modified >>>>>> the project.rake_task to be 'spec' rather than commented out, >>>> however >>>>>> it seems that CC.rb now tries to run my spec's over the >>>>>> production >>>>>> database rather than the test database. >>>>>> >>>>>> Running a 'rake spec' from the command line with the same project >>>>>> works fine as expected, however unfortunately through CC.rb it >>>> fails. >>>>>> >>>>>> Anyone got any thoughts where things might be wrong with the >>>>>> configuration of what database to use? or any pointers where to >>>> take >>>>>> a look? >>>>>> >>>>>> Thanks for any thoughts, ideas. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Marcus >>>>>> _______________________________________________ >>>>>> Cruisecontrolrb-users mailing list >>>>>> Cruisecontrolrb-users at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >>>>>> >>>>> >>>>> >>>>> -- >>>>> Jeff Xiong >>>>> Software Journeyman - http://gigix.thoughtworkers.org >>>>> Open Source Contributor - http://cruisecontrolrb.thoughtworks.com/ >>>>> Technical Evangelist - http://www.infoq.com/cn/ >>>>> _______________________________________________ >>>>> Cruisecontrolrb-users mailing list >>>>> Cruisecontrolrb-users at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >>>> >>>> _______________________________________________ >>>> Cruisecontrolrb-users mailing list >>>> Cruisecontrolrb-users at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >>>> >>>> ___________________________________________________________________ >>>> ___ >>>> This email has been scanned by the MessageLabs Email Security >>>> System. >>>> For more information please visit http://www.messagelabs.com/email >>>> ___________________________________________________________________ >>>> ___ >>>> >>>> _______________________________________________ >>>> Cruisecontrolrb-users mailing list >>>> Cruisecontrolrb-users at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >>> >>> _______________________________________________ >>> Cruisecontrolrb-users mailing list >>> Cruisecontrolrb-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > From dmg2n at virginia.edu Tue Apr 17 16:28:19 2007 From: dmg2n at virginia.edu (Duane Gran) Date: Tue, 17 Apr 2007 16:28:19 -0400 Subject: [Cruisecontrolrb-users] undefined method error Message-ID: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> I'm using CCRB 1.1 and I've confirmed that I can run "rake test RAILS_ENV=test" in my work directory with success, but the build log always shows the following error: /p0/users/dmg2n/cruisecontrolrb-1.1.0/projects/collex/work dmg2n$ ruby -e require 'rubygems' rescue nil; require 'rake'; load '/p0/ users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake'; ARGV << '-- nosearch' << 'cc:build'; Rake.application.run /p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake:20: undefined method `namespace' for main:Object (NoMethodError) from -e:1:in `load' from -e:1 dir : /p0/users/dmg2n/cruisecontrolrb-1.1.0/projects/collex/work command : ruby -e "require 'rubygems' rescue nil; require 'rake'; load '/p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run" executed command : echo /p0/users/dmg2n/cruisecontrolrb-1.1.0/ projects/collex/work dmg2n$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load '/p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/ cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run" >> /p0/users/dmg2n/cruisecontrolrb-1.1.0/ projects/collex/build-1255.1/build.log && ruby -e "require 'rubygems' rescue nil; require 'rake'; load '/p0/users/dmg2n/ cruisecontrolrb-1.1.0/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run" >> /p0/users/dmg2n/ cruisecontrolrb-1.1.0/projects/collex/build-1255.1/build.log 2>&1 exitstatus: 1 I'm building this on Solaris with the ruby package from blastwave.org, which has worked well for me thus far. I have the latest gem version. Is anyone familiar with this error? Thanks. Duane -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4210 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070417/4b2cfea0/attachment.bin From gedanken at io.com Wed Apr 18 08:17:16 2007 From: gedanken at io.com (Gedanken) Date: Wed, 18 Apr 2007 07:17:16 -0500 (CDT) Subject: [Cruisecontrolrb-users] [off topic?] Not sure where my installation is messed up In-Reply-To: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> References: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> Message-ID: <20070418070444.C15389@eris.io.com> I don't know where the error is, but I apologize if this is off topic. Im just at my wits end and too new to RoR and CruiseControl to get much further. I have an installation with cruisecontrol.rb and a project Ill call WebAbb. Cc.rb seemed to be workign fine, and I was using a build_my_app script in my config to do extra cool stuff, like use Capistrano to deploy it from /usr/local/cruisecontrol/projects/WebApp to /var/www/WebApp, and copy over a database.yml, etc. Everything was working great. Then, I created a second project in cc.rb, which was the DEMO svn tag of the same project. It deploys to /var/www/WebApp-demo/ Cruise control seemed to handle it great... and I fire up a second web server with a slightly different lighttpd.conf file to serve it up. I made it so port 80 serves the demo version, and 8080 serves up the latest HEAD of the project so we have sort of a test and staging situation. The problem is this - the web server on 8080 is serving up the wrong pages. There are radical differences between the DEMO and HEAD versions, so it is immediately obvious visually. It is not using the code in WebApp. It is not using the code in WebAppDemo. I have NO IDEA where it is getting the code it is displaying. It feels like something somewhere has old versions cached, fastcgi I assume. i have tried killing and restarting everything under the sun. Suspiciously, I dont see a fastcgi process for the HEAD (the one thats messed up), just demo root at envy:/var/www/WebApp/current/log# ps -ef | grep dispatch bob 18089 27406 6 Apr13 ? 07:19:53 ruby /usr/local/cruisecontrolrb-1.0.0/public/dispatch.fcgi bob 8858 28176 0 07:55 ? 00:00:02 /usr/local/bin/ruby /var/www/WebApp-demo/current/public/dispatch.fcgi Where is my WebApp dispatch.fcgi? Why is this workign at all without it? Where is it gettign these radically out of date (but clearly from HEAD not DEMO) pages to serve?? Ive checked every log I can think of and restarted everything, even installing these projects from scratch after blowing away the directories. Help?? -- gedanken From dmg2n at virginia.edu Wed Apr 18 08:29:29 2007 From: dmg2n at virginia.edu (Duane Gran) Date: Wed, 18 Apr 2007 08:29:29 -0400 Subject: [Cruisecontrolrb-users] undefined method error In-Reply-To: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> References: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> Message-ID: <4F4EFBCC-7EF9-450A-B922-AD501D9F0DEF@virginia.edu> All, I solved this problem. Here is how... The rake package from blastwave.org was version 0.6. Even though "gem list" showed 0.7.2, so I removed the blastwave package and then things worked correctly. Additionally I had to enter the following environment line into my cruise_config.rb: ENV['RAILS_ENV'] = 'test' I hope this is helpful for anyone else trying to get things going on Solaris. Duane On Apr 17, 2007, at 4:28 PM, Duane Gran wrote: > I'm using CCRB 1.1 and I've confirmed that I can run "rake test > RAILS_ENV=test" in my work directory with success, but the build > log always shows the following error: > > /p0/users/dmg2n/cruisecontrolrb-1.1.0/projects/collex/work dmg2n$ > ruby -e require 'rubygems' rescue nil; require 'rake'; load '/p0/ > users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake'; ARGV << '-- > nosearch' << 'cc:build'; Rake.application.run > /p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake:20: > undefined method `namespace' for main:Object (NoMethodError) > from -e:1:in `load' > from -e:1 > > dir : /p0/users/dmg2n/cruisecontrolrb-1.1.0/projects/collex/work > command : ruby -e "require 'rubygems' rescue nil; require 'rake'; > load '/p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/cc_build.rake'; > ARGV << '--nosearch' << 'cc:build'; Rake.application.run" > executed command : echo /p0/users/dmg2n/cruisecontrolrb-1.1.0/ > projects/collex/work dmg2n$ ruby -e "require 'rubygems' rescue nil; > require 'rake'; load '/p0/users/dmg2n/cruisecontrolrb-1.1.0/tasks/ > cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; > Rake.application.run" >> /p0/users/dmg2n/cruisecontrolrb-1.1.0/ > projects/collex/build-1255.1/build.log && ruby -e "require > 'rubygems' rescue nil; require 'rake'; load '/p0/users/dmg2n/ > cruisecontrolrb-1.1.0/tasks/cc_build.rake'; ARGV << '--nosearch' << > 'cc:build'; Rake.application.run" >> /p0/users/dmg2n/ > cruisecontrolrb-1.1.0/projects/collex/build-1255.1/build.log 2>&1 > exitstatus: 1 > > I'm building this on Solaris with the ruby package from > blastwave.org, which has worked well for me thus far. I have the > latest gem version. Is anyone familiar with this error? Thanks. > > Duane_______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4210 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070418/5ff04b8b/attachment-0001.bin From dmg2n at virginia.edu Wed Apr 18 12:55:18 2007 From: dmg2n at virginia.edu (Duane Gran) Date: Wed, 18 Apr 2007 12:55:18 -0400 Subject: [Cruisecontrolrb-users] documentation suggestion Message-ID: <07A1945F-95C0-4224-BA2D-9914D076C870@virginia.edu> Because I'm filing more of a sysadmin role than as a ruby developer I overlooked a nuance that is probably obvious to others, but edits to config/site_config.rb require a restart of CC-rb. I was banging my head on the wall wondering why none of my smtp auth settings made any difference. :( A suggestion would be to note this requirement in manual (http:// cruisecontrolrb.thoughtworks.com/documentation/manual) under the "build monitoring via email" section. I hope the suggestion is useful. Maybe a better route would be so that it was dynamically re- loaded, but I'm not sure if that is practical. Duane -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4210 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070418/d7511a84/attachment.bin From jeremystellsmith at gmail.com Thu Apr 19 00:40:47 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Wed, 18 Apr 2007 21:40:47 -0700 Subject: [Cruisecontrolrb-users] [off topic?] Not sure where my installation is messed up In-Reply-To: <20070418070444.C15389@eris.io.com> References: <449BBE88-2DA3-4AAA-9890-75817FE5FB1B@virginia.edu> <20070418070444.C15389@eris.io.com> Message-ID: it sounds like this is a bit off topic, but what i would do is 1) verify that the code in /var/www/WebApp-demo/ is the demo code you expect it to be. if it is, then ccrb is working. 2) stop the server at 8080, so only the demo one should be working and look at what should be the demo from a browser 3) delete the source for /var/www/WebApp/ and look at the demo in a browser . . . These things are hard to track down, just keep going and question all your assumptions. Good luck, Jeremy On 4/18/07, Gedanken wrote: > > > I don't know where the error is, but I apologize if this is off topic. Im > just at my wits end and too new to RoR and CruiseControl to get much > further. > > I have an installation with cruisecontrol.rb and a project Ill call > WebAbb. Cc.rb seemed to be workign fine, and I was using a build_my_app > script in my config to do extra cool stuff, like use Capistrano to deploy > it from /usr/local/cruisecontrol/projects/WebApp to /var/www/WebApp, and > copy over a database.yml, etc. Everything was working great. > > Then, I created a second project in cc.rb, which was the DEMO svn tag of > the same project. It deploys to /var/www/WebApp-demo/ > > Cruise control seemed to handle it great... and I fire up a second web > server with a slightly different lighttpd.conf file to serve it up. I > made it so port 80 serves the demo version, and 8080 serves up the latest > HEAD of the project so we have sort of a test and staging situation. > > The problem is this - the web server on 8080 is serving up the wrong > pages. There are radical differences between the DEMO and HEAD > versions, so it is immediately obvious visually. It is not using the code > in WebApp. It is not using the code in WebAppDemo. I have NO IDEA where > it is getting the code it is displaying. > > It feels like something somewhere has old versions cached, fastcgi I > assume. i have tried killing and restarting everything under the sun. > Suspiciously, I dont see a fastcgi process for the HEAD (the one thats > messed up), just demo > > root at envy:/var/www/WebApp/current/log# ps -ef | grep dispatch > bob 18089 27406 6 Apr13 ? 07:19:53 ruby > /usr/local/cruisecontrolrb-1.0.0/public/dispatch.fcgi > bob 8858 28176 0 07:55 ? 00:00:02 /usr/local/bin/ruby > /var/www/WebApp-demo/current/public/dispatch.fcgi > > Where is my WebApp dispatch.fcgi? Why is this workign at all without it? > Where is it gettign these radically out of date (but clearly from HEAD not > DEMO) pages to serve?? > > Ive checked every log I can think of and restarted everything, even > installing these projects from scratch after blowing away the directories. > > Help?? > > -- > gedanken > _______________________________________________ > 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/20070418/d54301f5/attachment.html From Jeffrey.Damick at revolution.com Thu Apr 19 12:04:57 2007 From: Jeffrey.Damick at revolution.com (Jeffrey Damick) Date: Thu, 19 Apr 2007 12:04:57 -0400 Subject: [Cruisecontrolrb-users] Ability to disable smtp tls Message-ID: Would you make an option to disable the TLS attempt for the action_mailer_tls plugin? For mail gateways that don't support 'STARTTLS' it throws an exception and doesn't fall back to non-tls. I commented out the require_dependency in the vendor/plugins/action_mailer_tls/init.rb to work around the issue, but a config switch would be great. Thanks, -jeff From msegvich at gmail.com Thu Apr 19 20:57:21 2007 From: msegvich at gmail.com (Matt Segvich) Date: Thu, 19 Apr 2007 19:57:21 -0500 Subject: [Cruisecontrolrb-users] consistently get segmentation fault Message-ID: <340b25110704191757h399cc114n1f3ac925d7343751@mail.gmail.com> I consistently get a daily core dump when running CruiseControl.rb. Note it's just the rails app that dies, not the builder process for the projects. I'm using 1.0 and haven't taken the time to upgrade to 1.1. Here's some info about our environment: Solaris 10 (x86) Ruby 1.8.5 (built from source) Here's the output for when it died on 3 different occasions. /usr/local/ruby/ruby-1.8.5/lib/ruby/1.8/timeout.rb:59: [BUG] Segmentation fault ./script/../config/../vendor/rails/actionpack/lib/action_view/helpers/text_helper.rb:26: [BUG] Segmentation fault ./script/../config/../vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:59: [BUG] Segmentation fault I started using the fastthread gem yesterday just on hunch that it might be threading related, but that didn't help. My belief is it really doesn't have anything to do with ccrb, but for whatever reason ccrb exposes the bug in Ruby or Rails rather quickly. Don't know if anyone else has experience this or has suggestions. Any help is appreciated. Matt Segvich From marcus at marcuscrafter.com Thu Apr 19 21:07:19 2007 From: marcus at marcuscrafter.com (Marcus Crafter) Date: Fri, 20 Apr 2007 11:07:19 +1000 Subject: [Cruisecontrolrb-users] consistently get segmentation fault In-Reply-To: <340b25110704191757h399cc114n1f3ac925d7343751@mail.gmail.com> References: <340b25110704191757h399cc114n1f3ac925d7343751@mail.gmail.com> Message-ID: <19A59DB4-7D13-429B-9E36-7773016E03FB@marcuscrafter.com> Hi Matt, I've had a similar problem, not with CC.rb but with Ruby seg faulting before under OSX on my older PowerBook - are you using GCC4 on your Solaris box by chance? http://crafterm.net/blog/articles/2006/11/24/segmentation-faults-with- ruby-1-8-4-in-fink-10-4-tree-with-gcc-4 In my case, rebuilding Ruby on my PowerBook without optimisation or using GCC 3 fixed it all up. Hope this helps somewhat. Cheers, Marcus On 20/04/2007, at 10:57 AM, Matt Segvich wrote: > I consistently get a daily core dump when running CruiseControl.rb. > Note it's just the rails app that dies, not the builder process for > the projects. I'm using 1.0 and haven't taken the time to upgrade to > 1.1. Here's some info about our environment: > > Solaris 10 (x86) > Ruby 1.8.5 (built from source) > > Here's the output for when it died on 3 different occasions. > > /usr/local/ruby/ruby-1.8.5/lib/ruby/1.8/timeout.rb:59: [BUG] > Segmentation fault > ./script/../config/../vendor/rails/actionpack/lib/action_view/ > helpers/text_helper.rb:26: > [BUG] Segmentation fault > ./script/../config/../vendor/rails/actionpack/lib/action_view/ > helpers/capture_helper.rb:59: > [BUG] Segmentation fault > > I started using the fastthread gem yesterday just on hunch that it > might be threading related, but that didn't help. My belief is it > really doesn't have anything to do with ccrb, but for whatever reason > ccrb exposes the bug in Ruby or Rails rather quickly. Don't know if > anyone else has experience this or has suggestions. Any help is > appreciated. > > Matt Segvich > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From dmg2n at virginia.edu Fri Apr 20 08:04:33 2007 From: dmg2n at virginia.edu (Duane Gran) Date: Fri, 20 Apr 2007 08:04:33 -0400 Subject: [Cruisecontrolrb-users] Ability to disable smtp tls In-Reply-To: References: Message-ID: I'll second this suggestion. On my config I resorted to creating a gmail account just so I could get around this issue. I was faced with the option of installing and configuring a cert for postfix, which seemed a bit onerous. For a localhost connection that has no authentication requirements I can't see any real value in using TLS to encrypt the payload. Duane On Apr 19, 2007, at 12:04 PM, Jeffrey Damick wrote: > > Would you make an option to disable the TLS attempt for the > action_mailer_tls plugin? For mail gateways that don't support > 'STARTTLS' > it throws an exception and doesn't fall back to non-tls. > > I commented out the require_dependency in the > vendor/plugins/action_mailer_tls/init.rb to work around the issue, > but a > config switch would be great. > > > Thanks, > -jeff > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4210 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070420/c2550e37/attachment-0001.bin From jeremystellsmith at gmail.com Fri Apr 20 11:33:38 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Fri, 20 Apr 2007 08:33:38 -0700 Subject: [Cruisecontrolrb-users] documentation suggestion In-Reply-To: <07A1945F-95C0-4224-BA2D-9914D076C870@virginia.edu> References: <07A1945F-95C0-4224-BA2D-9914D076C870@virginia.edu> Message-ID: we should probably just put a note in the file itself, yeah? then as you edit it, you'll notice it. I'll add it. I'm a very experienced developer and a very familiar w/ cruise, and I've gotten bitten by this before :) thanks for the feedback, Jeremy On 4/18/07, Duane Gran wrote: > > Because I'm filing more of a sysadmin role than as a ruby developer I > overlooked a nuance that is probably obvious to others, but edits to > config/site_config.rb require a restart of CC-rb. I was banging my > head on the wall wondering why none of my smtp auth settings made any > difference. :( > > A suggestion would be to note this requirement in manual (http:// > cruisecontrolrb.thoughtworks.com/documentation/manual) under the > "build monitoring via email" section. I hope the suggestion is > useful. Maybe a better route would be so that it was dynamically re- > loaded, but I'm not sure if that is practical. > > Duane > _______________________________________________ > 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/20070420/d73a33fd/attachment.html From maui at ideeli.com Fri Apr 27 11:24:01 2007 From: maui at ideeli.com (Mark Uhrmacher) Date: Fri, 27 Apr 2007 11:24:01 -0400 Subject: [Cruisecontrolrb-users] Problem with CC and rails_cron Message-ID: Hi everyone, I'm having a problem with CC with a plugin that creates its own table in init.rb. I can run rake RAILS_ENV=test db:test:purge;rake RAILS_ENV=test db:migrate; rake test from /projects/ without an error. However, I get an error right after the successful migration in the CC build.log as follows: [CruiseControl] Invoking Rake task "test" /usr/local/bin/ruby18 -Ilib:test "/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake/rake_test_loader.rb" "test/unit/ecard_test.rb" "test/unit/color_test.rb" "test/unit/user_test.rb" "test/unit/common_question_test.rb" "test/unit/product_test.rb" "test/unit/image_test.rb" "test/unit/subscription_test.rb" "test/unit/blog_image_test.rb" "test/unit/post_test.rb" "test/unit/promotion_test.rb" "test/unit/carrier_test.rb" "test/unit/cart_test.rb" "test/unit/service_test.rb" "test/unit/offer_test.rb" "test/unit/comment_test.rb" "test/unit/sku_test.rb" "test/unit/sms_test.rb" "test/unit/batch_sms_test.rb" "test/unit/faq_test.rb" "test/unit/blog_comment_test.rb" "test/unit/line_item_test.rb" "test/unit/job_test.rb" "test/unit/gateway_subscription_notification_test.rb" "test/unit/entrant_test.rb" "test/unit/call_test.rb" "test/unit/order_test.rb" "test/unit/sweepstake_test.rb" "test/unit/category_test.rb" "test/unit/update_notification_test.rb" "test/unit/update_email_test.rb" "test/unit/invitation_test.rb" "test/unit/request_for_notification_test.rb" "test/unit/related_site_test.rb" -- create_table("rails_crons") -> 0.0048s -- add_column(:rails_crons, :concurrent, :boolean) -> 0.0232s /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1789:in `method_missing': undefined method `concurrent=' for # (NoMethodError) from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1510:in `send' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1510:in `attributes=' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1509:in `each' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1509:in `attributes=' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1354:in `initialize_without_callbacks' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/callbacks.rb:236:in `initialize' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:406:in `new' from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:406:in `create' ... 12 levels... from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' from /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake/rake_test_loader.rb:5 from /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake/rake_test_loader.rb:5:in `each' from /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake/rake_test_loader.rb:5 /usr/local/bin/ruby18 -Ilib:test "/usr/local/lib/ruby/gems/1.8/gems/rake- 0.7.2/lib/rake/rake_test_loader.rb" "test/functional/landing_controller_test.rb" "test/functional/store_controller_test.rb" "test/functional/update_emails_controller_test.rb" "test/functional/sms_controller_test.rb" "test/functional/admin_controller_test.rb" "test/functional/ivr_controller_test.rb" Loaded suite /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake/rake_test_loader Started It is worth noting that the rails cron plugin has its own internal migration in its init.rb: ------- vendor/plugin/rails_cron/init.rb start ------ require "rails_cron" require "acts_as_background" ActiveRecord::Base.send :include, ActsAsBackground unless RailsCron.table_exists? ActiveRecord::Schema.create_table(RailsCron.table_name) do |t| t.column :command, :text t.column :start, :integer t.column :finish, :integer t.column :every, :integer end end unless RailsCron.content_columns.map{|a|a.name}.include? "concurrent" ActiveRecord::Schema.add_column :rails_crons, :concurrent, :boolean end --- end file -- Any idea why these builds are failing? Environment: FreeBSD 6 CC 1.1 Rails 1.1.6 Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070427/46f34f61/attachment.html