Story #17535
Updated by Peter Amstutz over 3 years ago
Somewhere in the Jenkins pipeline after development packages are built:
1) Spin up a Jenkins worker from a slim image (possibly multiple OS versions)
2) Run provision.sh / salt to install and configure Arvados on the worker
3) Run the diagnostics + smoke tests (hasher pipeline)
4) Report results
5) Shut everything down