-
Notifications
You must be signed in to change notification settings - Fork 347
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 (encrypted) SSH Key to Travis-CI for (Continuous) Deployment #42
Comments
Last night I spent around 4h trying to debug using an SSH Key (with a passphrase) on Travis-CI ... Essentially: having a
My conclusion is that I need to open a StackOverflow Question for this and move on! This is wasting my time! 😞 |
Posted this question: https://stackoverflow.com/questions/50542947/how-to-run-ssh-commands-from-bash-when-rsa-key-has-a-password Now I'm going to try this using an RSA Key without a |
On advice from "chepner" on SO I'm trying out |
Ok, I've "wrestled" with this "long enough". I really wish I had someone to pair on this with ... 😞 |
On the advice of @pynexj I'm trying: https://github.com/clarkwang/passh Just reading the source https://github.com/clarkwang/passh/blob/master/passh.c now ... |
The script compiles: (but then Travis can't find the executable...) So now I'm trying to use Enter passphrase for key './deploy_key': looks like I'm "back to square one" ... 😢 |
OK ... I've opened an issue on the
|
Using an RSA Key without a Let's crack on with this! 👍 |
This is totes working and PR is ready for review. 👍 |
In order to deploy "review apps" from Travis-CI we need to:
.travis.yml
file to decrypt the key before attempting to deploythankfully, I've done this before (and documented it): https://github.com/healthlocker/healthlocker/blob/a57d2741ae703b45ac8eb8465305a6e327baa152/continuous-deployment.md#encrypted-ssh-key-for-deployment
so it should be reasonably "easy" (there are a couple more steps this time...)
travis
user has the necessary permissions to perform the deploy.The text was updated successfully, but these errors were encountered: