BTW, here's what I see after install a local instance of cruise and building via the web interface:
dberger:/home/dberger >ps -ef | grep build | grep -v grep | grep village dberger 25625 19459 0 14:45 ? 00:00:00 ruby /home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/cruise build globe_village dberger 28170 25625 0 15:07 ? 00:00:00 sh -c echo /home/dberger/.cruise/projects/globe_village/work dberger$ ruby\ -e \ \"require\ \'rubygems\'\ rescue\ nil\;\ require\ \'rake\'\;\ load\ \'/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake \'\;\ ARGV\ \<\<\ \'--nosearch\'\ \<\<\ \'cc:build\'\;\ Rake.application.run\;\ ARGV.clear\" >> /home/dberger/.cruise/projects/globe_village/build-0dca885.2/build.log && >> ruby -e "require 'rubygems' rescue nil; require 'rake'; load >> '/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake'; ARGV >> << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> >> /home/dberger/.cruise/projects/globe_village/build-0dca885.2/build.log 2>&1 On Mon, 2011-01-24 at 15:03 -0700, Daniel Berger wrote: > Not that I can see. We do have multiple watchers setup that are pointing > at the same project but different branches. > > Hm, is it possible we have projects setup pointing at the same branch by > mistake? Is there a way to tell? Would that cause it? > > Regards, > > Dan > > On Mon, 2011-01-24 at 10:41 -0700, Alexey Verkhovsky wrote: > > It's not configured anywhere, moreover is not supposed to happen. But > > then, running the same build twice is not supposed to happen, either. > > ps -ef | grep build should tell you all you need. > > > > On Mon, Jan 24, 2011 at 10:26 AM, Daniel Berger <[email protected]> > > wrote: > > Hi, > > > > Can you help me determine if that's the case? Where is that > > configured? > > > > Dan > > > > > > On Mon, 2011-01-24 at 10:14 -0700, Alexey Verkhovsky wrote: > > > Are you running two builder processes for the same project? > > > > > > On Mon, Jan 24, 2011 at 9:28 AM, Daniel Berger > > <[email protected]> > > > wrote: > > > Hi, > > > > > > Ruby 1.8.7 > > > Cruise Control 1.4.0 > > > Passenger 3.0.2 > > > git > > > > > > Since upgrading to Passenger 3 we've noticed that > > our Cruise > > > projects > > > try to run the test suite twice which is, in itself, > > causing > > > some of our > > > tests to fail (on the second run). > > > > > > Note that our tests pass (and only run once) on our > > local > > > boxes, so it's > > > not some hidden fork call. Also, they pass if run > > manually on > > > the server > > > hosting CC (and only run once). It's only the > > automated > > > testing that > > > exhibits this behavior. > > > > > > Any ideas? > > > > > > Regards, > > > > > > Dan > > > > > > _______________________________________________ > > > Cruisecontrolrb-users mailing list > > > [email protected] > > > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > > > > > -- > > > Alexey Verkhovsky > > > http://alex-verkhovsky.blogspot.com/ > > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > > > _______________________________________________ > > > Cruisecontrolrb-users mailing list > > > [email protected] > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > > > -- > > Alexey Verkhovsky > > http://alex-verkhovsky.blogspot.com/ > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
