tree ecdcf14dfead11be2d8c4f4cd7e91a4d33e6d032
parent 07650989469aa4b204908713ebc4d82e92fde92a
author Neels Hofmeyr <nhofmeyr@sysmocom.de> 1494719845 +0200
committer Neels Hofmeyr <nhofmeyr@sysmocom.de> 1494851037 +0000

contrib: rethink jenkins jobs with build slave approach

Previously, the idea was to run a test remotely via SSH. This has moved to
operating an actual jenkins build slave on the main unit, which simplifies
things.

Also, previously (in the old osmo-gsm-tester), there was a daemon running,
accepting new trials by a directory appearing. Now, we're directly launching a
test run, which simplifies things.

Remove all SSH stuff from the "run" script.

Compose the checksums of the built binary-tars in the actual build jobs. In the
"run" job, only combine those checksums to one file. (Otherwise we would
compose the sums after transmitting over the network to the build slave.)

Instead of storing trials in a common location on the system, just keep one
trial in the workspace per run. After the run, tar up the trial dir to enable
easy archiving of build results.

The common location on the system might still be a good idea if we're one day
going to move to concurrent runs with scheduling of hardware resources, but so
far we're having simple one-shot runs.

Change-Id: I129f5189ce2bebd761bc752b158fb8778b31010e