view · edit · sidebar · attach · print · history

20130611-jobs

<< | Index | >>


Summary

  • Try to make jobs work on funtoo

Commits

Index


Make the jobs work on vagrant funtoo

  • jobs/import_bsv

Got disabling UPDATER in log file. Why? Restartet vagrant & job. Now the documents are starting to come in.

But at the end I still have disabling UPDATER. Is this okay?

loading testenvironment

DEVELOPER_HOST = smtp.hispeed.ch
DEVELOPER_MAIL = niklaus.giger@hispeed.ch

disabling UPDATER
/var/www/oddb.org/log/job.pid is created
process: /var/www/oddb.org/jobs/import_bsv_followers
init system
init system: 30.717535869
setup drb-delegation
/var/www/oddb.org/log/job.pid is deleted
real    99m25.239s
user    40m50.643s
sys     7m43.549s

Problem cannot configure Savon logging

  • Savon has the same error Message: undefined method `configure' for Savon:Module whether we use Version 2.1.0 or 1.2.0.

Version on thinpower is 0.9.7. Savon got refactored in 0.9.8. But Savon.configure is still documented in the master branch. But you cannot find anymore the def self.configure in lib/savon.rb. And in Version 1.x it changed the signature to def configure.

Savon mentions in docs/version2.md that the global configure method has gone. ext/swissindex/src/swissindex.rb calls Savon.configure to change the logging. savon/docs/version2.md hast this paragraph about logging

 
#### Logger

Was replaced with Ruby's standard Logger. The custom Logger was removed for simplicity. You can
still set the global `:log_level` and `:filters` options or active `:pretty_print_xml`.

I think we should really think about creating a jenkins daily jobs which calls bundle update and tries to run test specification to catch changes in underlying gems as soon as possible.

setup migel

  • Added static-modules/oddb/manifests.pp to setup migel
    • Git clone /var/www/migel
    • Add daemontools service migeld
    • Must create PostgreSQL db and role migel
    • Try cloning puppetmodule postgresql and adapt it to run under funtoo.

This proved to be easy. See Attach:gentoo_patch.txt and https://github.com/ngiger/puppet-postgres/commits/master, but showed that even when the default setting for postgresql are under /etc/postgresql-8.4 we were running a client 9.2. Therefore decided to adapt the rest of the vagrant setup to postgresql module.

  • For still unknown reasons it seems that the puppet module does not work, e.g. no psql statements are executed. Therefore I revert the commit c2692e6301c3e4970b506b31846d12cb9f7494ec 'Added migel and puppetlabs-postgresq' to add the statements by hand.
view · edit · sidebar · attach · print · history
Page last modified on June 12, 2013, at 08:35 AM