Detect release before application initializers run

[eugeneius]

The release can be set manually by the user. The typical way to do that would be to create an initializer:

# config/initializers/raven.rb
Raven.configure do |config|
  config.release = ENV['RELEASE']
end

The hook in the Rails integration that tries to automatically detect a release is run after the app's initializers, which means it clobbers any value that has already been set - even if it can't detect a release, it sets the value back to nil.

If the user has set a release themselves, we shouldn't try to detect it.

[nateberkopec]

Ack, that's definitely not intended.

The problem is with a Cap-deployed app with a .git folder. In that case, when the client is initialized, we set the release to the short Git SHA ("asdaf" or whatever). project_root only gets properly set when Rails is initialized, which happens after the client is initialized, so that's why I was re-running detect_release with a bare =.

[eugeneius]

Okay, I've taken a different approach here: we now set project_root and try to detect the release before the application initializers are run.

The before_initialize hook was added in Rails 3.0, which is the oldest version we support. Both Rails.logger and Rails.root are available when it runs.

[nateberkopec]

Thanks!