-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add build support #13
Conversation
I think this is more or less what we wanted now. I'll update the docs to reflect the changes for rake/heroku users. |
Awesome, when will this be released? |
Does the usage of this match what you expect/wanted from it @snmaynard ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see maze integration tests here. The interface/usage looks ok.
rescue | ||
logger.important("Bugnsag deploy notification failed, #{$!.inspect}") | ||
logger.important("Bugnsag release notification failed, #{$!.inspect}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bugnsag
:api_key => fetch(:bugsnag_api_key, ENV["BUGSNAG_API_KEY"]), | ||
:app_version => fetch(:app_version, ENV["BUGSNAG_APP_VERSION"]), | ||
:auto_assign_release => fetch(:bugsnag_auto_assign_release, nil), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why no ENV var?
after "deploy", "bugsnag:deploy" | ||
after "deploy:migrations", "bugsnag:deploy" | ||
after "deploy", "bugsnag:release" | ||
after "deploy:migrations", "bugsnag:release" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont know why there is deploy:migrations here too.
:api_key => fetch(:bugsnag_api_key, ENV["BUGSNAG_API_KEY"]), | ||
:app_version => fetch(:app_version, ENV["BUGSNAG_APP_VERSION"]), | ||
:auto_assign_release => fetch(:bugsnag_auto_assign_release), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be env var here
:api_key => fetch(:bugsnag_api_key, ENV["BUGSNAG_API_KEY"]), | ||
:app_version => fetch(:app_version, ENV["BUGSNAG_APP_VERSION"]), | ||
:auto_assign_release => fetch(:bugsnag_auto_assign_release, ENV["BUGSNAG_AUTO_ASSIGN_RELEASE"]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tested the env variable. I dont think it will work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks about ready. Blocking bits:
require "pp"
present in the capistrano2 integration and the exampleCapfiles
- The docs suggest using
require: false
when adding bugsnag-cap to a Gemfile, but that isn't done in the examples - there's no need for the "with/without Bugsnag" bits in the tests
@@ -1,26 +1,31 @@ | |||
require 'pp' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this from debugging?
Is covering the case where Capistrano can pull configuration details from Bugsnag-Ruby not required? |
ah, nvm the last bit about the tests. I thought it hadn't been updated to match since it uses doubles now. |
Here is what I have so far.
I removed the heroku support in favour of documenting the CLI. I have also removed rake support as this should be focused on capistrano imo. This is currently untested but I think directionally ok. Thoughts @Cawllec?