Travis deploy setup #42
Conversation
bmarkons
force-pushed
the
travis-setup
branch
9 times, most recently
from
877f8a7
to
a94f9d0
Compare
| chmod 600 /tmp/deploy_rsa; | ||
| ssh-add /tmp/deploy_rsa; | ||
|
|
||
| ssh -o StrictHostKeyChecking=no root@$RUNNER_HOST "tsp git -C ./ruby-bench-docker pull --rebase origin master && tsp ./ruby-bench-docker/deploy/script"; |
There was a problem hiding this comment.
Deploy is also queued as tsp task.
There was a problem hiding this comment.
Which server is this being built on?
There was a problem hiding this comment.
Bare metal - where suites are being run.
I am not doing push to docker hub, just pulling latest changes and rebuilding images.
There was a problem hiding this comment.
Hmm better to build this on the web server. The bare metal server might be running benchmarks and building can be CPU intensive affecting the results
There was a problem hiding this comment.
The bare metal server might be running benchmarks and building can be CPU intensive affecting the results
For that reason I enqueue deploy task through tcp, to ensure no suite is running when deploy is in progress. Have a look at this line we are commenting on ⬆️
There was a problem hiding this comment.
better to build this on the web server
I am building images on bare metal server since that's where they are being used. We don't need docker images on web server.
The alternative way would be to build those on Travis and push them to docker hub.
There was a problem hiding this comment.
Yea lets build on Travis instead even though it might be slower. We should try and keep the bare-metal free from running any other services except fro benchmarks.
No description provided.