Using Travis-CI for Continuous Delivery with Edeliver & Destillery
Opened this issue · 13 comments
- Deploy to VM using SSH
- [-] Environment Variables for Instance IP Address? (or is this pointless "obfuscation"...?)
- [-] Environment Variables for username? (not required)
- Add Deployment
privatekey to Travis-CI (encrypted)
Connection timed out during banner exchange
Failed to detect generated release at
root@213.168.248.157:/home/ubuntu/hello_world_edeliver/builds
Please set RELEASE_DIR in the config file to fix that,
or check that the APP variable is set correctly.
Appears to be the same issue as: https://elixirforum.com/t/elixir-deployment-problem/4542
Without any changes it worked the next time I ran it ...
Would prefer to understand why! but going to ride the wave for now and question it later!
Install:
sudo apt-get install ruby-full -y
sudo gem install travis
Success:
touch .travis.yml && travis encrypt-file ~/.ssh/deploy_key --add
if you see:
not logged in - try running travis login --org
Login to your GitHub in the CLI:
https://travis-ci.org/nelsonic/hello_world_edeliver/builds/258721596#L678
elixir failed with exit status 255
https://stackoverflow.com/questions/1405324/how-to-create-a-bash-script-to-check-the-ssh-connection
ssh -q ubuntu@213.168.248.157 exit && echo $?
https://travis-ci.org/nelsonic/hello_world_edeliver/builds/258732237#L722
The authenticity of host '213.168.248.157 (213.168.248.157)' can't be established.
ECDSA key fingerprint is 3e:0d:6a:fd:2c:0f:1a:bb:55:8b:28:e6:64:84:10:02.
Are you sure you want to continue connecting (yes/no)?
https://superuser.com/questions/125324/how-can-i-avoid-sshs-host-verification-for-known-hosts
ssh -o "StrictHostKeyChecking no" -q ubuntu@213.168.248.157 exit && echo $?
https://travis-ci.org/nelsonic/hello_world_edeliver/builds/258753539#L539
The command "openssl aes-256-cbc -K $encrypted_78685c75019b_key -iv $encrypted_78685c75019b_iv -in deploy_key.enc -out ~\/.ssh/deploy_key -d" failed and exited with 1 during .
read through: https://docs.travis-ci.com/user/encrypting-files/ not v. insightful as to the error ... 😞
This is still relevant to a "production" deploy.
But I think we nearly have a much better way of doing this ... #ACID 😉