Use devspace as validator rather then omero-build?

[joshmoore]

Currently omero-build is the primary repository for checking the build status of downstream PRs, leading it to have a more complicated travis script, see https://github.com/ome/omero-build/blob/master/travis.sh

Adding in Bio-Formats to that script would further complicate matters. Perhaps this repository is a more natural location for that. However, to do so, it will be necessary to either spin up a devspace and check its status with a single script or run parts of this repository with less overhead.

---

• Auto-register for JDK without needing to enter ci/ext/oracle credentials
• Generate snoopy token to not need to pass a SOURCE location

[joshmoore]

As a starting point for the spin-up variant, here's a script I'm currently working from:

#!/usr/bin/env bash
set -e
set -u
set -x

SOURCE=$1
TOPIC=$2
test -e pipeline-configs.yaml
test -e slave/.ssh || cp -nr $SOURCE/.ssh slave/
test -e slave/.gitconfig || cp -nr $SOURCE/.gitconfig slave/
HOST_IP=$(histname -I | cut -f1 -d" ")
./sslcert jenkins/sslcert $HOST_IP
./sslcert nginx/sslcert $HOST_IP
python ./rename.py $TOPIC

PASSWORD=$(openssl rand -hex 32)
sed -i "s/JENKINS_PASSWORD=devspace/JENKINS_PASSWORD=$PASSWORD/" .env

git commit -a -m "Local changes for $TOPIC"

echo PASSWORD: $PASSWORD

[joshmoore]

As a starting point for the "run parts" variant, @manics found:

https://github.com/jenkinsci/jenkinsfile-runner