Quality/QA-tools/QAReports/Setting up the development environment

Introduction

QA Reports is a Ruby on Rails application so you need to install a bunch of stuff to get it up and running. This draft documentation is based on experiences in installation on Ubuntu 10.10

Installing Ruby

Most likely you won't succeed with the packaged version of Ruby. Thus this guide uses Ruby Version Manager (rvm).

1. Install dependencies: $ sudo apt-get install git-core curl
2. Install rvm: $ bash < <( curl http://rvm.beginrescueend.com/releases/rvm-install-head )
3. Follow the instructions printed once installation is ready
   1. Install needed packages - check section "For Ruby (MRI & ree) you should install the following OS dependencies"
   2. Enable loading of rvm - check section "You must now complete the install by loading RVM in new shells"
      1. Edit .bashrc as described
      2. Restart your shell to have rvm enabled
4. Install Ruby: $ rvm install 1.8.7
5. Set into use: $ rvm use 1.8.7

Set up QA Reports

1. Clone qa-reports from git: $ git clone git://gitorious.org/meego-quality-assurance/qa-reports.git
2. Install preqrequisites: $ sudo apt-get install libmysqlclient-dev
3. Create database config to qa-reports/config/database.yml (example exists by name database.example.yml)

Follow the instructions then from qa-reports/README.creole:

1. $ gem update --system
   1. Note: if you get an error about zlib, follow these instructions
2. $ gem install bundler --no-ri --no-rdoc
3. $ bundle install --without staging production
4. $ rake db:create
5. $ rake db:migrate
   1. Failed, but after rerun worked
6. Start the server: $ rails server
   1. And see it fail due to problems with RubyGem rack

TODO: Fix the gem "rack" issue. Currently during bundling output like this is produced:

 Using rack (1.2.1) from git://github.com/rack/rack.git (at master) 
 rack at /home/poikajar/.rvm/gems/ruby-1.8.7-p330/bundler/gems/rack-672396f0fdaa did not have a valid gemspec.
 This prevents bundler from installing bins or native extensions, but that may not affect its   functionality.
 The validation message from Rubygems was:
   ["SPEC"] are not files

The above seems to be related to this issue which should've been solved. If editing rubygems manually from that path bundler does not complain but still the result is the same when trying to start the server.

And when trying to start the server the output is:

 /home/poikajar/.rvm/rubies/ruby-1.8.7-p330/lib/ruby/site_ruby/1.8/rubygems.rb:812:in `report_activate_error': 
 Could not find RubyGem rack (~> 1.2.1) (Gem::LoadError)