Upgrade to Rails 3.2.
Nest job in job_type hash.

Rails 3.2 changed our json output a bit. This implements a custom
as_json method so the output matches what we got before.
Set MERGE_MASTER correctly for xen plugins.

Fix an issue where the Xen plugins for branches were installed
but not merged w/ master correctly. Previously we'd only get
trunk code into the plugins if someone rebased their own code.
Deploy as smokestack user.
Drop URL to smokestack.openstack.org in header.

No need to link to self like this.
Catch ActiveRecord::ActiveRecordError in job retry

Update our job retry loops to look for ActiveRecord::ActiveRecordError
instead of ActiveRecord::RecordNotFound. We do this because
Rails 3.1 was throwing ActiveRecord::StatementInvalid so the thought
here is we'll just catch the base ActiveRecord exception class instead.
Make limits query parameter on jobs page sticky.

Fixes an issue where the ?limit= query parameter would not
persist on an AJAX refresh.
Update about page for Rails 3.2.
Set reconnect: true in database.yml.sample.

We need this enabled for Resque.
Add job clone feature/button to jobs page.
Revert "Catch ActiveRecord::ActiveRecordError in job retry"

This reverts commit 9232e243ac423f3231d3c4f1e914cb2b69ec0418.
Remove reconnect in database.yaml.sample.

We don't need/want this after all.
Git ignore public/assets.
Parse project revisions in a single pass.

Previously we iterated over stdout to parse each project/build
revision. This changes to code so that a single pass is used
to parse the revisions.

Adds extra tests on parsing revision too.
Add build failure status.

Adds support for build failure tracking. Build failures (failure
to build an RPM, Deb, etc.) will now get tracked as 'BuildFail'
instead of just a normal 'Failure'.

Includes a new orange box icon to help highlight these failures in the
UI.
Detect build failures in the job_group.
Add resque after_fork SQL connection fix.

After resque forks we need to verify active connections. This
seems to resolve some reconnect issues that slipped in when we
switched to Rails 3.2.
Bump to latest stable Rails release.
Add test failure status.

Adds support for test failure tracking. Test failures (failure
to run a test suite like Torpedo or Tempest) will now get tracked as
'TestFail' instead of just a normal 'Failure'.

Includes a pink hexagon icon to help highlight these failures in
the UI.
Bump to kytoon 1.4.1.