Skip to content
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

Merged
merged 11 commits into from
Mar 20, 2018
Merged

Add build support #13

merged 11 commits into from
Mar 20, 2018

Conversation

snmaynard
Copy link
Contributor

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?

@Cawllec Cawllec mentioned this pull request Feb 1, 2018
@Cawllec
Copy link
Contributor

Cawllec commented Feb 8, 2018

I think this is more or less what we wanted now. I'll update the docs to reflect the changes for rake/heroku users.

@boena
Copy link

boena commented Feb 8, 2018

Awesome, when will this be released?

@Cawllec
Copy link
Contributor

Cawllec commented Feb 26, 2018

Does the usage of this match what you expect/wanted from it @snmaynard ?

Copy link
Contributor Author

@snmaynard snmaynard left a 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}")
Copy link
Contributor Author

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),
Copy link
Contributor Author

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"
Copy link
Contributor Author

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),
Copy link
Contributor Author

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"]),
Copy link
Contributor Author

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.

Copy link
Contributor

@kattrali kattrali left a 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 example Capfiles
  • 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'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this from debugging?

@kattrali kattrali changed the title WIP build support Add build support Mar 20, 2018
@kattrali kattrali changed the base branch from master to next March 20, 2018 11:03
@Cawllec
Copy link
Contributor

Cawllec commented Mar 20, 2018

Is covering the case where Capistrano can pull configuration details from Bugsnag-Ruby not required?

@kattrali
Copy link
Contributor

ah, nvm the last bit about the tests. I thought it hadn't been updated to match since it uses doubles now.

@kattrali kattrali merged commit 7bef303 into next Mar 20, 2018
@kattrali kattrali deleted the build-support branch March 20, 2018 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants