From amitkkulkarni.84 at gmail.com Mon Jan 3 09:24:09 2011 From: amitkkulkarni.84 at gmail.com (Amit Kulkarni) Date: Mon, 3 Jan 2011 19:54:09 +0530 Subject: [Cruisecontrolrb-users] Email configuration for projects Message-ID: Hi, I had successfully added a project but i am getting problem in email setup. I am getting error as"Error in plugin EmailNotifier: wrong number of arguments (3 for 2)" This is the log : error] [2011-01-03 19:45:47] Error sending e-mail - current server settings are : :authentication = :plain :password = "test123" :port = 587 :address = "smtp.gmail.com" :user_name = "test at joshsoftware.com" :enable_starttls_auto = true [error] [2011-01-03 19:45:47] Error sending e-mail - current server settings are : :authentication = :plain :password = "test123" :port = 587 :address = "smtp.gmail.com" :user_name = "test at joshsoftware.com" :enable_starttls_auto = true [error] wrong number of arguments (3 for 2) [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in `check_auth_args' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in `do_start' [error] /usr/lib/ruby/1.8/net/smtp.rb:525:in `start' [error] /usr/lib/ruby/1.8/net/smtp.rb:463:in `start' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:565:in `perform_delivery_smtp' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in `send' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in `deliver!' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:333:in `method_missing' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in `send' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in `email' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:41:in `build_finished' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in `send' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in `notify' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in `collect' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in `notify' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:313:in `build_without_serialization' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:289:in `build' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:268:in `build_if_requested' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:26:in `check_build_request_until_next_polling' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:13:in `run' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:79 [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78:in `catch' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78 [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in `load' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in `builder' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in `send' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in `run' [error] /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../cruise:5 My site_config file is as follows : ActionMailer::Base.smtp_settings = { :address => "smtp.gmail.com", :port => 587, :authentication => :plain, :enable_starttls_auto => true, :user_name => "test at joshsoftware.com", :password => "test123" } and my cruise_config file is as follows : Project.configure do |project| # Send email notifications about broken and fixed builds to email1 at your.site, email2 at your.site (default: send to nobody) project.email_notifier.emails = ['qa at joshsoftware.com'] project.email_success_notifier.emails = ['qa at joshsoftware.com'] # Set email 'from' field to john at doe.com: project.email_notifier.from = 'test at test.com' # Build the project by invoking rake task 'custom' # project.rake_task = 'custom' # Build the project by invoking shell script "build_my_app.sh". Keep in mind that when the script is invoked, # current working directory is [cruise data]/projects/your_project/work, so if you do not keep build_my_app.sh # in version control, it should be '../build_my_app.sh' instead # project.build_command = 'build_my_app.sh' # Ping Subversion for new revisions every 5 minutes (default: 30 seconds) # project.scheduler.polling_interval = 5.minutes end Can you suggest where i am going wrong.Or some gem is missing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Mon Jan 3 11:22:42 2011 From: thewoolleyman at gmail.com (Chad Woolley) Date: Mon, 3 Jan 2011 09:22:42 -0700 Subject: [Cruisecontrolrb-users] Email configuration for projects In-Reply-To: References: Message-ID: On Mon, Jan 3, 2011 at 7:24 AM, Amit Kulkarni wrote: > Hi, > I had successfully added a project but i am getting problem in email setup. > I am getting error as"Error in plugin EmailNotifier: wrong number of > arguments (3 for 2)" Does this happen to be RubyEE? There was a recent commit which looks related: commit bfc8a8fb0511eaa9c1d62d9120b79d76414117e2 Author: Alex Verkhovsky Date: Fri Nov 12 00:03:07 2010 -0700 in RubyEE 2010.02, instance_method() is called method() Can you check out the latest from github and see if that fixes the problem? Good Luck, -- Chad From christopher.gaudig at dfki.de Mon Jan 3 10:28:31 2011 From: christopher.gaudig at dfki.de (Christopher Gaudig) Date: Mon, 03 Jan 2011 16:28:31 +0100 Subject: [Cruisecontrolrb-users] Email configuration for projects In-Reply-To: References: Message-ID: <4D21EB1F.1080202@dfki.de> Hi! I think this should help: https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/209-fail-to-send-auth-tls-mail-ruby-1-8-7 Good luck! On 01/03/2011 03:24 PM, Amit Kulkarni wrote: > Hi, > I had successfully added a project but i am getting problem in email setup. > I am getting error as"Error in plugin EmailNotifier: wrong number of > arguments (3 for 2)" > > This is the log : > error] [2011-01-03 19:45:47] Error sending e-mail - current server > settings are : > :authentication = :plain > :password = "test123" > :port = 587 > :address = "smtp.gmail.com " > :user_name = "test at joshsoftware.com " > :enable_starttls_auto = true > [error] [2011-01-03 19:45:47] Error sending e-mail - current server > settings are : > :authentication = :plain > :password = "test123" > :port = 587 > :address = "smtp.gmail.com " > :user_name = "test at joshsoftware.com " > :enable_starttls_auto = true > [error] wrong number of arguments (3 for 2) > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in > `check_auth_args' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in > `do_start' > [error] /usr/lib/ruby/1.8/net/smtp.rb:525:in `start' > [error] /usr/lib/ruby/1.8/net/smtp.rb:463:in `start' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:565:in > `perform_delivery_smtp' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in > `deliver!' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:333:in > `method_missing' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in > `email' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:41:in > `build_finished' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in > `notify' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in > `collect' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in > `notify' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:313:in > `build_without_serialization' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:289:in > `build' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:268:in > `build_if_requested' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:26:in > `check_build_request_until_next_polling' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:13:in > `run' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:79 > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78:in > `catch' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78 > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in > `load' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in > `builder' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in > `run' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../cruise:5 > > > My site_config file is as follows : > ActionMailer::Base.smtp_settings = { > :address => "smtp.gmail.com ", > :port => 587, > :authentication => :plain, > :enable_starttls_auto => true, > :user_name => "test at joshsoftware.com ", > :password => "test123" > } > > and my cruise_config file is as follows : > Project.configure do |project| > > # Send email notifications about broken and fixed builds to > email1 at your.site, email2 at your.site (default: send to nobody) > project.email_notifier.emails = ['qa at joshsoftware.com > '] > project.email_success_notifier.emails = ['qa at joshsoftware.com > '] > > # Set email 'from' field to john at doe.com : > project.email_notifier.from = 'test at test.com ' > > # Build the project by invoking rake task 'custom' > # project.rake_task = 'custom' > > # Build the project by invoking shell script "build_my_app.sh". Keep > in mind that when the script is invoked, > # current working directory is > [cruise data]/projects/your_project/work, so if you do not > keep build_my_app.sh > # in version control, it should be '../build_my_app.sh' instead > # project.build_command = 'build_my_app.sh' > > # Ping Subversion for new revisions every 5 minutes (default: 30 seconds) > # project.scheduler.polling_interval = 5.minutes > > end > > Can you suggest where i am going wrong.Or some gem is missing. > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -- Christopher Gaudig Underwater & Space Robotics DFKI GmbH Robotics Innovation Center Robert-Hooke-Stra?e 5 28359 Bremen, Germany Phone: +49 (0)421 178 45-4119 Fax: +49 (0)421 178 45-4150 E-Mail: christopher.gaudig at dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- German Research Center for Artificial Intelligence Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 From amitkkulkarni.84 at gmail.com Tue Jan 4 09:56:05 2011 From: amitkkulkarni.84 at gmail.com (Amit Kulkarni) Date: Tue, 4 Jan 2011 20:26:05 +0530 Subject: [Cruisecontrolrb-users] Email configuration for projects In-Reply-To: <4D21EB1F.1080202@dfki.de> References: <4D21EB1F.1080202@dfki.de> Message-ID: Hi, I downloaded the plugin and made the changes required.But on running the build i am getting the error as wrong number of arguments (8 for 6) at /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/plugins/action_mailer_optional_tls/lib/action_mailer_tls.rb:10:in `start' I had made the following changes : Under /vendor/plugins/action_mailer_optional_tls$ if VERSION == '1.8.6' check_auth_args user, secret, authtype if user or secret elsif VERSION == '1.8.7' check_auth_args user, secret if user or secret end And under site_config Following are the settings : ActionMailer::Base.smtp_settings = { :address => "smtp.gmail.com", :port => 587, :authentication => :plain, #:enable_starttls_auto => true, :tls => true, :user_name => "test at joshsoftware.com", :password => "test" } On Mon, Jan 3, 2011 at 8:58 PM, Christopher Gaudig < christopher.gaudig at dfki.de> wrote: > Hi! > > I think this should help: > https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/209-fail-to-send-auth-tls-mail-ruby-1-8-7 > > Good luck! > > > > > On 01/03/2011 03:24 PM, Amit Kulkarni wrote: > >> Hi, >> I had successfully added a project but i am getting problem in email >> setup. >> I am getting error as"Error in plugin EmailNotifier: wrong number of >> arguments (3 for 2)" >> >> This is the log : >> error] [2011-01-03 19:45:47] Error sending e-mail - current server >> settings are : >> :authentication = :plain >> :password = "test123" >> :port = 587 >> :address = "smtp.gmail.com " >> :user_name = "test at joshsoftware.com " >> >> :enable_starttls_auto = true >> [error] [2011-01-03 19:45:47] Error sending e-mail - current server >> settings are : >> :authentication = :plain >> :password = "test123" >> :port = 587 >> :address = "smtp.gmail.com " >> :user_name = "test at joshsoftware.com " >> >> :enable_starttls_auto = true >> [error] wrong number of arguments (3 for 2) >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in >> `check_auth_args' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in >> `do_start' >> [error] /usr/lib/ruby/1.8/net/smtp.rb:525:in `start' >> [error] /usr/lib/ruby/1.8/net/smtp.rb:463:in `start' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:565:in >> `perform_delivery_smtp' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in >> `deliver!' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:333:in >> `method_missing' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in >> `email' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:41:in >> `build_finished' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in >> `notify' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in >> `collect' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in >> `notify' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:313:in >> `build_without_serialization' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:289:in >> `build' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:268:in >> `build_if_requested' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:26:in >> `check_build_request_until_next_polling' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:13:in >> `run' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:79 >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78:in >> `catch' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78 >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in >> `load' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in >> `builder' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in >> `run' >> [error] >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../cruise:5 >> >> >> My site_config file is as follows : >> ActionMailer::Base.smtp_settings = { >> :address => "smtp.gmail.com ", >> >> :port => 587, >> :authentication => :plain, >> :enable_starttls_auto => true, >> :user_name => "test at joshsoftware.com ", >> >> :password => "test123" >> } >> >> and my cruise_config file is as follows : >> Project.configure do |project| >> >> # Send email notifications about broken and fixed builds to >> email1 at your.site, email2 at your.site (default: send to nobody) >> project.email_notifier.emails = ['qa at joshsoftware.com >> '] >> >> project.email_success_notifier.emails = ['qa at joshsoftware.com >> '] >> >> # Set email 'from' field to john at doe.com : >> project.email_notifier.from = 'test at test.com ' >> >> >> # Build the project by invoking rake task 'custom' >> # project.rake_task = 'custom' >> >> # Build the project by invoking shell script "build_my_app.sh". Keep >> in mind that when the script is invoked, >> # current working directory is >> [cruise data]/projects/your_project/work, so if you do not >> keep build_my_app.sh >> # in version control, it should be '../build_my_app.sh' instead >> # project.build_command = 'build_my_app.sh' >> >> # Ping Subversion for new revisions every 5 minutes (default: 30 >> seconds) >> # project.scheduler.polling_interval = 5.minutes >> >> end >> >> Can you suggest where i am going wrong.Or some gem is missing. >> >> >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > > > -- > Christopher Gaudig > Underwater & Space Robotics > > DFKI GmbH > Robotics Innovation Center > Robert-Hooke-Stra?e 5 > 28359 Bremen, Germany > > Phone: +49 (0)421 178 45-4119 > Fax: +49 (0)421 178 45-4150 > E-Mail: christopher.gaudig at dfki.de > > Weitere Informationen: http://www.dfki.de/robotik > ----------------------------------------------------------------------- > German Research Center for Artificial Intelligence > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH > Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern > Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster > (Vorsitzender) Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes > Amtsgericht Kaiserslautern, HRB 2313 > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973 > Steuernummer: 19/673/0060/3 > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christopher.gaudig at dfki.de Tue Jan 4 10:09:29 2011 From: christopher.gaudig at dfki.de (Christopher Gaudig) Date: Tue, 04 Jan 2011 16:09:29 +0100 Subject: [Cruisecontrolrb-users] Email configuration for projects In-Reply-To: References: <4D21EB1F.1080202@dfki.de> Message-ID: <4D233829.4010101@dfki.de> Did you remove lib/smtp_tls.rb and install the action_mailer_optional_tls plugin and restart cruise? If yes, I can't help, I'm afraid. http://jira.public.thoughtworks.org/browse/CCRB-187 On 01/04/2011 03:56 PM, Amit Kulkarni wrote: > Hi, > I downloaded the plugin and made the changes required.But on running the > build i am getting the error as > wrong number of arguments (8 for 6) at > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/plugins/action_mailer_optional_tls/lib/action_mailer_tls.rb:10:in > `start' > > I had made the following changes : > Under /vendor/plugins/action_mailer_optional_tls$ > > if VERSION == '1.8.6' > check_auth_args user, secret, authtype if user or secret > elsif VERSION == '1.8.7' > check_auth_args user, secret if user or secret > end > > And under site_config Following are the settings : > ActionMailer::Base.smtp_settings = { > :address => "smtp.gmail.com ", > :port => 587, > :authentication => :plain, > #:enable_starttls_auto => true, > :tls => true, > :user_name => "test at joshsoftware.com ", > :password => "test" > } > > > On Mon, Jan 3, 2011 at 8:58 PM, Christopher Gaudig > > wrote: > > Hi! > > I think this should help: > https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/209-fail-to-send-auth-tls-mail-ruby-1-8-7 > > Good luck! > > > > > On 01/03/2011 03:24 PM, Amit Kulkarni wrote: > > Hi, > I had successfully added a project but i am getting problem in > email setup. > I am getting error as"Error in plugin EmailNotifier: wrong number of > arguments (3 for 2)" > > This is the log : > error] [2011-01-03 19:45:47] Error sending e-mail - current server > settings are : > :authentication = :plain > :password = "test123" > :port = 587 > :address = "smtp.gmail.com > " > :user_name = "test at joshsoftware.com > >" > > :enable_starttls_auto = true > [error] [2011-01-03 19:45:47] Error sending e-mail - current server > settings are : > :authentication = :plain > :password = "test123" > :port = 587 > :address = "smtp.gmail.com > " > :user_name = "test at joshsoftware.com > >" > > :enable_starttls_auto = true > [error] wrong number of arguments (3 for 2) > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in > `check_auth_args' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in > `do_start' > [error] /usr/lib/ruby/1.8/net/smtp.rb:525:in `start' > [error] /usr/lib/ruby/1.8/net/smtp.rb:463:in `start' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:565:in > `perform_delivery_smtp' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in > `deliver!' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:333:in > `method_missing' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in > `email' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:41:in > `build_finished' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in > `notify' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in > `collect' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in > `notify' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:313:in > `build_without_serialization' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:289:in > `build' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:268:in > `build_if_requested' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:26:in > `check_build_request_until_next_polling' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:13:in > `run' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:79 > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78:in > `catch' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78 > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in > `load' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in > `builder' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in > `send' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in > `run' > [error] > /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../cruise:5 > > > My site_config file is as follows : > ActionMailer::Base.smtp_settings = { > :address => "smtp.gmail.com > ", > > :port => 587, > :authentication => :plain, > :enable_starttls_auto => true, > :user_name => "test at joshsoftware.com > >", > > :password => "test123" > } > > and my cruise_config file is as follows : > Project.configure do |project| > > # Send email notifications about broken and fixed builds to > email1 at your.site, email2 at your.site (default: send to nobody) > project.email_notifier.emails = ['qa at joshsoftware.com > > >'] > > project.email_success_notifier.emails = > ['qa at joshsoftware.com > >'] > > # Set email 'from' field to john at doe.com > >: > project.email_notifier.from = 'test at test.com > >' > > > # Build the project by invoking rake task 'custom' > # project.rake_task = 'custom' > > # Build the project by invoking shell script > "build_my_app.sh". Keep > in mind that when the script is invoked, > # current working directory is > [cruise data]/projects/your_project/work, so if > you do not > keep build_my_app.sh > # in version control, it should be '../build_my_app.sh' instead > # project.build_command = 'build_my_app.sh' > > # Ping Subversion for new revisions every 5 minutes (default: > 30 seconds) > # project.scheduler.polling_interval = 5.minutes > > end > > Can you suggest where i am going wrong.Or some gem is missing. > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > -- > Christopher Gaudig > Underwater & Space Robotics > > DFKI GmbH > Robotics Innovation Center > Robert-Hooke-Stra?e 5 > 28359 Bremen, Germany > > Phone: +49 (0)421 178 45-4119 > Fax: +49 (0)421 178 45-4150 > E-Mail: christopher.gaudig at dfki.de > > Weitere Informationen: http://www.dfki.de/robotik > ----------------------------------------------------------------------- > German Research Center for Artificial Intelligence > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH > Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern > Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster > (Vorsitzender) Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes > Amtsgericht Kaiserslautern, HRB 2313 > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973 > Steuernummer: 19/673/0060/3 > > > _______________________________________________ > 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 -- Christopher Gaudig Underwater & Space Robotics DFKI GmbH Robotics Innovation Center Robert-Hooke-Stra?e 5 28359 Bremen, Germany Phone: +49 (0)421 178 45-4119 Fax: +49 (0)421 178 45-4150 E-Mail: christopher.gaudig at dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- German Research Center for Artificial Intelligence Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 From amitkkulkarni.84 at gmail.com Wed Jan 5 01:31:28 2011 From: amitkkulkarni.84 at gmail.com (Amit Kulkarni) Date: Wed, 5 Jan 2011 12:01:28 +0530 Subject: [Cruisecontrolrb-users] Email configuration for projects In-Reply-To: <4D233829.4010101@dfki.de> References: <4D21EB1F.1080202@dfki.de> <4D233829.4010101@dfki.de> Message-ID: Hi, Yes, i did that and also restarted the cruise but i am getting following error : Could not load project configuration: undefined method `email_success_notifier' for # in /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:110:in `method_missing' On Tue, Jan 4, 2011 at 8:39 PM, Christopher Gaudig < christopher.gaudig at dfki.de> wrote: > Did you remove lib/smtp_tls.rb and install the action_mailer_optional_tls > plugin and restart cruise? > > If yes, I can't help, I'm afraid. > > http://jira.public.thoughtworks.org/browse/CCRB-187 > > > > > On 01/04/2011 03:56 PM, Amit Kulkarni wrote: > >> Hi, >> >> I downloaded the plugin and made the changes required.But on running the >> build i am getting the error as >> wrong number of arguments (8 for 6) at >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/plugins/action_mailer_optional_tls/lib/action_mailer_tls.rb:10:in >> `start' >> >> I had made the following changes : >> Under /vendor/plugins/action_mailer_optional_tls$ >> >> if VERSION == '1.8.6' >> check_auth_args user, secret, authtype if user or secret >> elsif VERSION == '1.8.7' >> check_auth_args user, secret if user or secret >> end >> >> And under site_config Following are the settings : >> ActionMailer::Base.smtp_settings = { >> :address => "smtp.gmail.com ", >> :port => 587, >> :authentication => :plain, >> #:enable_starttls_auto => true, >> :tls => true, >> >> :user_name => "test at joshsoftware.com ", >> :password => "test" >> } >> >> >> On Mon, Jan 3, 2011 at 8:58 PM, Christopher Gaudig >> > wrote: >> >> Hi! >> >> I think this should help: >> >> https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/209-fail-to-send-auth-tls-mail-ruby-1-8-7 >> >> Good luck! >> >> >> >> >> On 01/03/2011 03:24 PM, Amit Kulkarni wrote: >> >> Hi, >> I had successfully added a project but i am getting problem in >> email setup. >> I am getting error as"Error in plugin EmailNotifier: wrong number >> of >> arguments (3 for 2)" >> >> This is the log : >> error] [2011-01-03 19:45:47] Error sending e-mail - current server >> settings are : >> :authentication = :plain >> :password = "test123" >> :port = 587 >> :address = "smtp.gmail.com >> " >> :user_name = "test at joshsoftware.com >> > >> >" >> >> :enable_starttls_auto = true >> [error] [2011-01-03 19:45:47] Error sending e-mail - current server >> settings are : >> :authentication = :plain >> :password = "test123" >> :port = 587 >> :address = "smtp.gmail.com >> " >> :user_name = "test at joshsoftware.com >> > >> >" >> >> :enable_starttls_auto = true >> [error] wrong number of arguments (3 for 2) >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in >> `check_auth_args' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/smtp_tls.rb:7:in >> `do_start' >> [error] /usr/lib/ruby/1.8/net/smtp.rb:525:in `start' >> [error] /usr/lib/ruby/1.8/net/smtp.rb:463:in `start' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:565:in >> `perform_delivery_smtp' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:451:in >> `deliver!' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../vendor/rails/actionmailer/lib/action_mailer/base.rb:333:in >> `method_missing' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:52:in >> `email' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../lib/builder_plugins/email_notifier.rb:41:in >> `build_finished' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:334:in >> `notify' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in >> `collect' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:332:in >> `notify' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:313:in >> `build_without_serialization' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:289:in >> `build' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/project.rb:268:in >> `build_if_requested' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:26:in >> `check_build_request_until_next_polling' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/../config/../app/models/polling_scheduler.rb:13:in >> `run' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:79 >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78:in >> `catch' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/../../script/builder:78 >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in >> `load' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:47:in >> `builder' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in >> `send' >> [error] >> >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../lib/cruise_control/init.rb:10:in >> `run' >> [error] >> /home/amit/Desktop/cruisecontrol-1.4.0/public/../config/../cruise:5 >> >> >> My site_config file is as follows : >> ActionMailer::Base.smtp_settings = { >> :address => "smtp.gmail.com >> ", >> >> :port => 587, >> :authentication => :plain, >> :enable_starttls_auto => true, >> :user_name => "test at joshsoftware.com >> > >> >", >> >> :password => "test123" >> } >> >> and my cruise_config file is as follows : >> Project.configure do |project| >> >> # Send email notifications about broken and fixed builds to >> email1 at your.site, email2 at your.site (default: send to nobody) >> project.email_notifier.emails = ['qa at joshsoftware.com >> >> >'] >> >> >> project.email_success_notifier.emails = >> ['qa at joshsoftware.com >> >'] >> >> >> # Set email 'from' field to john at doe.com >> >: >> >> project.email_notifier.from = 'test at test.com >> > >> >' >> >> >> # Build the project by invoking rake task 'custom' >> # project.rake_task = 'custom' >> >> # Build the project by invoking shell script >> "build_my_app.sh". Keep >> in mind that when the script is invoked, >> # current working directory is >> [cruise data]/projects/your_project/work, so if >> you do not >> keep build_my_app.sh >> # in version control, it should be '../build_my_app.sh' instead >> # project.build_command = 'build_my_app.sh' >> >> # Ping Subversion for new revisions every 5 minutes (default: >> 30 seconds) >> # project.scheduler.polling_interval = 5.minutes >> >> end >> >> Can you suggest where i am going wrong.Or some gem is missing. >> >> >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> >> >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> >> >> >> -- >> Christopher Gaudig >> Underwater & Space Robotics >> >> DFKI GmbH >> Robotics Innovation Center >> Robert-Hooke-Stra?e 5 >> 28359 Bremen, Germany >> >> Phone: +49 (0)421 178 45-4119 >> Fax: +49 (0)421 178 45-4150 >> E-Mail: christopher.gaudig at dfki.de >> >> >> Weitere Informationen: http://www.dfki.de/robotik >> ----------------------------------------------------------------------- >> German Research Center for Artificial Intelligence >> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH >> Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern >> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster >> (Vorsitzender) Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes >> Amtsgericht Kaiserslautern, HRB 2313 >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973 >> Steuernummer: 19/673/0060/3 >> >> >> _______________________________________________ >> 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 >> > > > -- > Christopher Gaudig > Underwater & Space Robotics > > DFKI GmbH > Robotics Innovation Center > Robert-Hooke-Stra?e 5 > 28359 Bremen, Germany > > Phone: +49 (0)421 178 45-4119 > Fax: +49 (0)421 178 45-4150 > E-Mail: christopher.gaudig at dfki.de > > Weitere Informationen: http://www.dfki.de/robotik > ----------------------------------------------------------------------- > German Research Center for Artificial Intelligence > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH > Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern > Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster > (Vorsitzender) Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes > Amtsgericht Kaiserslautern, HRB 2313 > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973 > Steuernummer: 19/673/0060/3 > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bil.kleb at nasa.gov Wed Jan 5 20:17:43 2011 From: bil.kleb at nasa.gov (Kleb, William L. (LARC-D305)) Date: Wed, 5 Jan 2011 19:17:43 -0600 Subject: [Cruisecontrolrb-users] Updating my CC.rb instance? Message-ID: <366C91B6-F937-41FE-8F73-FA36AEB3F0ED@nasa.gov> Hi, According to https://github.com/thoughtworks/cruisecontrol.rb#readme the last release was 1.5 years ago: v1.4 on 2009-06-30. What version of Ruby and Rails should I use with that release? Should I instead just pull something from github? If so, what version of Ruby and Rails do you advise? Thanks, -- Bil, http://fun3d.larc.nasa.gov P.S. I'm currently using some hacked up v1.3 version I forked off github a long while ago. From dberger at globe.gov Mon Jan 24 11:28:02 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 09:28:02 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 Message-ID: <1295886482.1732.59.camel@globe-hw4whh1> 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 From alexey.verkhovsky at gmail.com Mon Jan 24 12:14:43 2011 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Mon, 24 Jan 2011 10:14:43 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295886482.1732.59.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> Message-ID: Are you running two builder processes for the same project? On Mon, Jan 24, 2011 at 9:28 AM, Daniel Berger 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 > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- Alexey Verkhovsky http://alex-verkhovsky.blogspot.com/ CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] -------------- next part -------------- An HTML attachment was scrubbed... URL: From dberger at globe.gov Mon Jan 24 12:26:24 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 10:26:24 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: References: <1295886482.1732.59.camel@globe-hw4whh1> Message-ID: <1295889984.1732.67.camel@globe-hw4whh1> 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 > 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 > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > -- > Alexey Verkhovsky > http://alex-verkhovsky.blogspot.com/ > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From alexey.verkhovsky at gmail.com Mon Jan 24 12:41:09 2011 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Mon, 24 Jan 2011 10:41:09 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295889984.1732.67.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> Message-ID: 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 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 > > 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 > > Cruisecontrolrb-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > -- > > Alexey Verkhovsky > > http://alex-verkhovsky.blogspot.com/ > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > _______________________________________________ > > 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 > -- Alexey Verkhovsky http://alex-verkhovsky.blogspot.com/ CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] -------------- next part -------------- An HTML attachment was scrubbed... URL: From dberger at globe.gov Mon Jan 24 17:03:38 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 15:03:38 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> Message-ID: <1295906618.1732.76.camel@globe-hw4whh1> 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 > 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 > > > 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 > > Cruisecontrolrb-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > -- > > Alexey Verkhovsky > > http://alex-verkhovsky.blogspot.com/ > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > _______________________________________________ > > 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 > > > > > -- > Alexey Verkhovsky > http://alex-verkhovsky.blogspot.com/ > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From dberger at globe.gov Mon Jan 24 17:12:57 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 15:12:57 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295906618.1732.76.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> Message-ID: <1295907177.1732.80.camel@globe-hw4whh1> 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 > > 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 > > > > > 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 > > > Cruisecontrolrb-users at rubyforge.org > > > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > > > > > -- > > > Alexey Verkhovsky > > > http://alex-verkhovsky.blogspot.com/ > > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > > > _______________________________________________ > > > 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 > > > > > > > > > > -- > > Alexey Verkhovsky > > http://alex-verkhovsky.blogspot.com/ > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > _______________________________________________ > > 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 dberger at globe.gov Mon Jan 24 17:21:15 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 15:21:15 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295906618.1732.76.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> Message-ID: <1295907675.1732.83.camel@globe-hw4whh1> BTW, I tried running this command (that showed up in ps -ef) from the command line manually in the work directory: 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" That worked fine. Regards, Dan 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 > > 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 > > > > > 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 > > > Cruisecontrolrb-users at rubyforge.org > > > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > > > > > -- > > > Alexey Verkhovsky > > > http://alex-verkhovsky.blogspot.com/ > > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > > > _______________________________________________ > > > 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 > > > > > > > > > > -- > > Alexey Verkhovsky > > http://alex-verkhovsky.blogspot.com/ > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > _______________________________________________ > > 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 dberger at globe.gov Mon Jan 24 18:17:23 2011 From: dberger at globe.gov (Daniel Berger) Date: Mon, 24 Jan 2011 16:17:23 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295907675.1732.83.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> Message-ID: <1295911043.1732.89.camel@globe-hw4whh1> Hi again, Invoking the build process from a local instance I see this: dberger 9330 25625 0 16:10 ? 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-28091f9.8/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-28091f9.8/build.log 2>&1 dberger 9331 9330 16 16:10 ? 00:00:09 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 dberger 22962 1 0 14:23 ? 00:00:01 ruby /home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/cruise build globe_village So, it looks like 2 processes there, 9330 and 9331. The latter has the former as its parent pid. I also tried switching to Passenger 2.x, but the result was the same. In addition, I tried altering the :cruise task to just do "puts hello" but it still seems to try to run the entire test suite. I slapped a debug print statement in the cruise control source to make sure it was picking up that there's a custom cruise task. It is. Any ideas? Regards, Dan On Mon, 2011-01-24 at 15:21 -0700, Daniel Berger wrote: > BTW, I tried running this command (that showed up in ps -ef) from the > command line manually in the work directory: > > 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" > > That worked fine. > > Regards, > > Dan > > 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 > > > 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 > > > > > > > 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 > > > > Cruisecontrolrb-users at rubyforge.org > > > > > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > > > > > > > > > > > > > -- > > > > Alexey Verkhovsky > > > > http://alex-verkhovsky.blogspot.com/ > > > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > > > > > > > -- > > > Alexey Verkhovsky > > > http://alex-verkhovsky.blogspot.com/ > > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > > > > _______________________________________________ > > > 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 > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From alexey.verkhovsky at gmail.com Mon Jan 24 20:26:13 2011 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Mon, 24 Jan 2011 18:26:13 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295911043.1732.89.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> Message-ID: On Mon, Jan 24, 2011 at 4:17 PM, Daniel Berger wrote: > So, it looks like 2 processes there, 9330 and 9331. The latter has the > former as its parent pid. > Looks exactly how it should. One is shell, the other one is ruby that it invoked. > 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. > Accessing the same database and/or some other resource(s), I presume? I'd bet that's the problem. To fix it, you want to configure CC.rb to serialize builds (i.e., make it so that only one build is running at any given time). There is a commented out setting for this in the site_config.rb, you just need to find and uncomment it. --Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From dberger at globe.gov Tue Jan 25 11:54:40 2011 From: dberger at globe.gov (Daniel Berger) Date: Tue, 25 Jan 2011 09:54:40 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> Message-ID: <1295974480.1732.94.camel@globe-hw4whh1> On Mon, 2011-01-24 at 18:26 -0700, Alexey Verkhovsky wrote: > On Mon, Jan 24, 2011 at 4:17 PM, Daniel Berger > wrote: > So, it looks like 2 processes there, 9330 and 9331. The latter > has the > former as its parent pid. > > Looks exactly how it should. One is shell, the other one is ruby that > it invoked. > > > > 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. > > > Accessing the same database and/or some other resource(s), I presume? > I'd bet that's the problem. To fix it, you want to configure CC.rb to > serialize builds (i.e., make it so that only one build is running at > any given time). There is a commented out setting for this in the > site_config.rb, you just need to find and uncomment it. I tried that but it didn't solve my problem unfortunately. This is tied to Passenger somehow I think, because when I run the build using WEBrick it only runs the tests once, and they pass. I'll play with our :cruise task some more and see if I can narrow it down. Regards, Dan From alexey.verkhovsky at gmail.com Tue Jan 25 15:21:53 2011 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Tue, 25 Jan 2011 13:21:53 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295974480.1732.94.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> <1295974480.1732.94.camel@globe-hw4whh1> Message-ID: When you catch it in the act of running the same build twice, I suggest that you look into the process tree and find out who started who. If it's not two concurrent builds running of different branches clashing with one another, then one of the build processes is probably an orphan. When you run this stuff under Passenger, it starts and stops frontend workers at will. These, in turn, start and stop builder processes, one per project. There is a protection mechanism in the form of a builder lock file, that is intended to prevent CC.rb from running multiple builders ob the same project directory; HOWEVER, if a builder process starts a build, which then doesn't die when the builder dies (say, a rescue Exception clause eating the stop signals, which are Exceptions in Ruby), you can end up with concurrent builds per project, I guess. Personally, I simply don't run CC.rb frontend under Passenger because of these oddball child process management scenarios. What I do instead is follow the instructions in daemon/cruise and let init run a single frontend process with a single set of builders. On Tue, Jan 25, 2011 at 9:54 AM, Daniel Berger wrote: > On Mon, 2011-01-24 at 18:26 -0700, Alexey Verkhovsky wrote: > > On Mon, Jan 24, 2011 at 4:17 PM, Daniel Berger > > wrote: > > So, it looks like 2 processes there, 9330 and 9331. The latter > > has the > > former as its parent pid. > > > > Looks exactly how it should. One is shell, the other one is ruby that > > it invoked. > > > > > > > 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. > > > > > > Accessing the same database and/or some other resource(s), I presume? > > I'd bet that's the problem. To fix it, you want to configure CC.rb to > > serialize builds (i.e., make it so that only one build is running at > > any given time). There is a commented out setting for this in the > > site_config.rb, you just need to find and uncomment it. > > I tried that but it didn't solve my problem unfortunately. This is tied > to Passenger somehow I think, because when I run the build using WEBrick > it only runs the tests once, and they pass. > > I'll play with our :cruise task some more and see if I can narrow it > down. > > Regards, > > Dan > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- Alexey Verkhovsky http://alex-verkhovsky.blogspot.com/ CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] -------------- next part -------------- An HTML attachment was scrubbed... URL: From dberger at globe.gov Tue Jan 25 15:37:52 2011 From: dberger at globe.gov (Daniel Berger) Date: Tue, 25 Jan 2011 13:37:52 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295974480.1732.94.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> <1295974480.1732.94.camel@globe-hw4whh1> Message-ID: <1295987872.1732.126.camel@globe-hw4whh1> On Tue, 2011-01-25 at 09:54 -0700, Daniel Berger wrote: > On Mon, 2011-01-24 at 18:26 -0700, Alexey Verkhovsky wrote: > > On Mon, Jan 24, 2011 at 4:17 PM, Daniel Berger > > wrote: > > So, it looks like 2 processes there, 9330 and 9331. The latter > > has the > > former as its parent pid. > > > > Looks exactly how it should. One is shell, the other one is ruby that > > it invoked. > > > > > > > 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. > > > > > > Accessing the same database and/or some other resource(s), I presume? > > I'd bet that's the problem. To fix it, you want to configure CC.rb to > > serialize builds (i.e., make it so that only one build is running at > > any given time). There is a commented out setting for this in the > > site_config.rb, you just need to find and uncomment it. > > I tried that but it didn't solve my problem unfortunately. This is tied > to Passenger somehow I think, because when I run the build using WEBrick Scratch that. It happens with WEBrick, too, but -only- if I daemonize it. Very peculiar. Investigating... Regards, Dan From dberger at globe.gov Tue Jan 25 16:55:36 2011 From: dberger at globe.gov (Daniel Berger) Date: Tue, 25 Jan 2011 14:55:36 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> <1295974480.1732.94.camel@globe-hw4whh1> Message-ID: <1295992536.1732.143.camel@globe-hw4whh1> On Tue, 2011-01-25 at 13:21 -0700, Alexey Verkhovsky wrote: > When you catch it in the act of running the same build twice, I > suggest that you look into the process tree and find out who started > who. If it's not two concurrent builds running of different branches > clashing with one another, then one of the build processes is probably > an orphan. > > When you run this stuff under Passenger, it starts and stops frontend > workers at will. These, in turn, start and stop builder processes, one > per project. There is a protection mechanism in the form of a builder > lock file, that is intended to prevent CC.rb from running multiple > builders ob the same project directory; HOWEVER, if a builder process > starts a build, which then doesn't die when the builder dies (say, a > rescue Exception clause eating the stop signals, which are Exceptions > in Ruby), you can end up with concurrent builds per project, I guess. > > Personally, I simply don't run CC.rb frontend under Passenger because > of these oddball child process management scenarios. What I do instead > is follow the instructions in daemon/cruise and let init run a single > frontend process with a single set of builders. I don't think this is related, but we've narrowed it down to this bit of code, added to a test helper library, that was added to dynamically add routes for testing: begin _routes = Our::Application.routes _routes.disable_clear_and_finalize = true _routes.clear! Our::Application.routes_reloader.paths.each{ |path| load(path) } _routes.draw do match "request404" => "application#request404" match "request500" => "application#request500" match "generic_request" => "application#generic_request" match "login_required_request" => "application#login_required_request" match "authorize_school_request" => "application#authorize_school_request" match "authorize_school_without_redirect_request" => "application#authorize_school_without_redirect_request" match "redirect_back_request" => "application#redirect_back_request" match "render_data_request" => "application#render_data_request" match "cancant_request" => "application#cancant_request" match "redirect" => "legacy#redirect" end ActiveSupport.on_load(:action_controller) do Our::Application.routes.finalize! end ensure _routes.disable_clear_and_finalize = false end If we comment this out, and the tests that use the helper, the problem goes away. BTW, I think the code came from http://openhood.com/rails/rails% 203/2010/07/20/add-routes-at-runtime-rails-3/ originally. Still tinkering with it... Regards, Dan From thewoolleyman at gmail.com Tue Jan 25 20:34:51 2011 From: thewoolleyman at gmail.com (Chad Woolley) Date: Tue, 25 Jan 2011 18:34:51 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> <1295974480.1732.94.camel@globe-hw4whh1> Message-ID: On Tue, Jan 25, 2011 at 1:21 PM, Alexey Verkhovsky wrote: > Personally, I simply don't run CC.rb frontend under Passenger because of > these oddball child process management scenarios. What I do instead is > follow the instructions in daemon/cruise and let init run a single frontend > process with a single set of builders. Also, if you use the init script './daemon/cruise [start|stop]', it is smart enough to kill all the child processes of your builders. Very handy. From dberger at globe.gov Wed Jan 26 12:07:40 2011 From: dberger at globe.gov (Daniel Berger) Date: Wed, 26 Jan 2011 10:07:40 -0700 Subject: [Cruisecontrolrb-users] CC running tests twice with Passenger 3 In-Reply-To: <1295992536.1732.143.camel@globe-hw4whh1> References: <1295886482.1732.59.camel@globe-hw4whh1> <1295889984.1732.67.camel@globe-hw4whh1> <1295906618.1732.76.camel@globe-hw4whh1> <1295907675.1732.83.camel@globe-hw4whh1> <1295911043.1732.89.camel@globe-hw4whh1> <1295974480.1732.94.camel@globe-hw4whh1> <1295992536.1732.143.camel@globe-hw4whh1> Message-ID: <1296061660.1724.16.camel@globe-hw4whh1> > > I don't think this is related, but we've narrowed it down to this bit of > code, added to a test helper library, that was added to dynamically add > routes for testing: > > begin > _routes = Our::Application.routes > _routes.disable_clear_and_finalize = true > _routes.clear! > > Our::Application.routes_reloader.paths.each{ |path| load(path) } > > _routes.draw do > match "request404" => "application#request404" > match "request500" => "application#request500" > match "generic_request" => "application#generic_request" > match "login_required_request" => > "application#login_required_request" > match "authorize_school_request" => > "application#authorize_school_request" > match "authorize_school_without_redirect_request" => > "application#authorize_school_without_redirect_request" > match "redirect_back_request" => "application#redirect_back_request" > match "render_data_request" => "application#render_data_request" > match "cancant_request" => "application#cancant_request" > > match "redirect" => "legacy#redirect" > end > ActiveSupport.on_load(:action_controller) do > Our::Application.routes.finalize! > end > ensure > _routes.disable_clear_and_finalize = false > end > > If we comment this out, and the tests that use the helper, the problem > goes away. > > BTW, I think the code came from http://openhood.com/rails/rails% > 203/2010/07/20/add-routes-at-runtime-rails-3/ originally. > > Still tinkering with it... I decided to remove this code and simply put the routes in the config/routes.rb file wrapped in an if block. That wasn't the issue, though. Based on my experiments, any attempt to reopen the ApplicationController class causes the double run behavior. There were some instance variables we wanted to get at directly, so we reopened the class and added some accessors. If I comment that code and the related tests, CC is suddenly happy again, even though they work fine from the command line. Why? I haven't a clue. Very bizarre. For now we're just going to comment them out and move on. Regards, Dan