This reverts commit d6d0c3c644.
Revert as it's not useful because the host doesn't accept ssh
connections. In this case, ssh will return exit code 0 but no work will
be done. It can be easily tested with "ssh sysmocom-downloads ls /"
which outputs nothing. Trying to acces a console through ssh errors
directly with a message.
Otherwise first time a machine+release combination is uploaded rsync
will fail:
sync --delete -avz tmp/deploy/ipk/ sysmocom-downloads:sysmocom-apu2/201705-nightly/ipk
sending incremental file list
rsync: mkdir "/home/generic/web-files/sysmocom-apu2/201705-nightly/ipk" failed: No such file or directory (2)
Create a Makefile that does the lifting of setting up the config
as it is done on the system. Handles the creation of the .ssh/config
for upload.
In the past upstream poned on such master Makefiles but as we
customize our build environment quite a bit it probably makes
sense and reduces the clone+set-up to two calls.