airbrake/airbrake — pull request #33 by cgriego (2011-11-11 17:26:06+00:00)
Title: Fix allowing airbrake_env/TO being different from rails_env/RAILS_ENV in deployment notifications

Deployment notifications were regressed In commit f12aa5355292a3ac8efbba2673c800e5aff067b3

By reusing the airbrake_env Capistrano variable for the RAILS_ENV environment variable, this has broken the whole reason the TO environment variable exists. For example, we have more named deployment environments (staging1, staging2, staging3) than we have Rails environment modes (staging) so they are not a 1 for 1 match. My deployments now fail because it's trying to load a Rails environment that doesn't exist.