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
Capistrano 3 Support seems broken #247
Comments
👍 |
1 similar comment
+1 |
Any progress on this? I'm having the same problem using Capistrano 3 with a Rails 4 app. |
+1 |
1 similar comment
+1 |
I'm using it on a production server now -- seems to be working fine. Didn't write tests or anything. Repo isn't being passed though, feel free to update the code |
👍 |
2 similar comments
+1 |
+1 |
+1 .. It's a pity that there seems to be no support.. |
The require should go in Capfile |
@ darrenterhune no, it doesn't |
I tried master branch. But, this seems to be still an issue. |
+1 |
1 similar comment
+1 |
Hey, I'm having an identical issue to the one described, even bundling the master branch version of the gem. Any ideas would be appreciated. |
Are you require capitrano3 in Capfile like this : require 'airbrake/capistrano3' ? |
Hey, so I happily don't get any errors when I deploy anymore. Thanks! I don't yet appear to be tracking deployments, though. Is there anything else I need to do in addition? (Forgive me if this is in Thanks Again, On Wed, Mar 26, 2014 at 3:01 AM, Olivier Kaluzny
|
Have you after :finished, 'airbrake:deploy' in your deploy.rb ? |
Ah, alright- so, that did it. Thanks, Olivier! I'm now tracking deployments. J I'm on Twitter: @Cropcho https://twitter.com/Cropcho On Wed, Mar 26, 2014 at 11:57 AM, Olivier Kaluzny
|
|
yeah, the above worked, thanks @chulkilee |
Closing this out.
|
The generator is still broken: #324 |
In a capistrano 3.0 project I try to get notifications about deployments.
so I have
but capistrano now failed with this message
Are you planning to support capistrano 3? At the moment the gemspec does not define a major version number of capistrano.
The text was updated successfully, but these errors were encountered: