2010-03-01 4 views
1

Je suis en train de mettre en place TeamCity 5.0.2 pour exécuter mes rails Projets specs (râteau juste spec)Mise en place TeamCity pour exécuter les rails spécifications

Ma configuration est:

  • git locale
  • rails racine app dans côté, il (git_root/site_root)

mes paramètres de coureur de coupe sont:

    chemin
  • à rakefile: site_root/Rakefile
  • répertoire de travail: site_root
  • tâches rake: spec
  • journalistes attachés: rspec

tout le reste est par défaut.

quand je lance la construction i obtenir la sortie suivante:

Checking for changes 
Clearing temporary directory: /home/michaelbaldry/Downloads/TeamCity/buildAgent/temp/buildTmp 
Checkout directory: /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41 
Updating sources: server side checkout... 
[Updating sources: server side checkout...] Building incremental patch for VCS root: local projects 
[Updating sources: server side checkout...] Repository sources transferred 
Starting build process in /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root 
/usr/bin/ruby /home/michaelbaldry/Downloads/TeamCity/buildAgent/plugins/rake-runner/lib/rb/runner/rakerunner.rb --rakefile /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/Rakefile spec SPEC_OPTS=--require 'teamcity/spec/runner/formatter/teamcity/formatter' --format Spec::Runner::Formatter::TeamcityFormatter:matrix 
(in /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root) 
LoadError: no such file to load -- /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/config/../vendor/rails/railties/lib/initializer Stacktrace: /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/config/boot.rb:45:in `load_initializer' /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/config/boot.rb:38:in `run' /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/config/boot.rb:11:in `boot!' /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/config/boot.rb:109 /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/Rakefile:4 /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2383:in `load' /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile' /home/michaelbaldry/Downloads/TeamCity/buildAgent/plugins/rake-runner/lib/rb/runner/rake_ext.rb:621:in `standard_exception_handling' /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile' /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run' /home/michaelbaldry/Downloads/TeamCity/buildAgent/plugins/rake-runner/lib/rb/runner/rake_ext.rb:621:in `standard_exception_handling' /home/michaelbaldry/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /home/michaelbaldry/Downloads/TeamCity/buildAgent/plugins/rake-runner/lib/rb/runner/rake_ext.rb:357:in `run' /home/michaelbaldry/Downloads/TeamCity/buildAgent/plugins/rake-runner/lib/rb/runner/rakerunner.rb:79 Source: /home/michaelbaldry/Downloads/TeamCity/buildAgent/work/65c3a24ba4d13a41/site_root/Rakefile:4 
Rake aborted! 
Process exit code: 1 
Build finished 

toute aide est très apprécié!

Répondre

1

J'ai eu un problème similaire. J'ai cliqué sur l'onglet "Build Log" et j'ai pu voir plus de détails que l'onglet "Overview".

J'ai trouvé un workaround:

gem uninstall test-unit 

Je ne peux pas dire que je l'aime cette solution, mais au moins cela a fonctionné. Le Build Log me conduit à google pour une constante non testée Test :: Unit :: TestResult :: TestResultFailureSupport qui m'a conduit à une autre ressource "uninitialized constant error" sur stackoverflow.com qui avait la solution.

Questions connexes