-
Notifications
You must be signed in to change notification settings - Fork 17
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
Support Capistrano 3.7.1? #26
Comments
Can you be more explicit? What is not supported? |
The error I had seems to have dissappeared, But I do see this:
This happens twice |
Ok, seems like a warning. I'll keep this issue open to take a look at it when I've got the time then. |
I also see:
|
Thanks, I'll take a look at that as well :) |
Hello, Thank you |
Sorry @NairolfL didn't get much time lately to work on OSS. If anyone wants to take this up, I'd be happy to review the PR. |
I think there was a breaking change in Cap v3.7.0. They now support an “SCM plugins” architecture: http://capistranorb.com/documentation/advanced-features/custom-scm/ |
I wrote a simple plugin for deploying via rsync in Capistrano 3.7+ (using the new “SCM plugins architecture”): https://gist.github.com/noniq/f73e7eb199a4c2ad519c6b5e2ba5b0df I might create a gem out of this if I find the time. In the meantime feel free to adapt & reuse. |
Very cool. Thanks for sharing! |
Nice @noniq :) If you want to use this repo for it, let me know! |
Thanks for the offer! It’s a rather breaking set of changes though, so I’m not sure if it’s a good idea to reuse this existing project for it, especially since I’m assuming that there are still plenty of people using Capistrano < 3.7 together with the current version of this project. I’ll think a bit more about it, happy to hear other thoughts on that, too! |
We can manage through the gem versioning I think for the breaking changes. It's time this repo embraces the updates of Capistrano ;) Let me know anyway, happy to talk about it. |
@noniq Just tested out your gist works great. In case is helpful for anyone else, our usage was to deploy tags or branches and noticed issues due to the inclusion of |
Hello - I've wrapped up @noniq's excellent gist into a straight-up Capistrano Plugin, which is available here. I had no idea how best to name it, so named it unimaginatively, and indicated in the readme that it's for 3.7.1+ plugin syntax. I've also included examples of use, especially how to hook local build processes into it, which is how I'm using it. It's on rubygems atm; I am happy to change/alter anything at request, or, indeed, receive feedback over at my Issues page. I've added @noniq as a listed author. Hope that isn't overstepping any bounds. |
@infovore Great, thanks a lot! 🎉 |
No description provided.
The text was updated successfully, but these errors were encountered: