defa683aba
This has several advantages: - we build and deploy the exact same environment that we use for testing, not just an approximation - we can (and do) cache the outcome, and have faster CI turn-arounds - we isolate the tooling better from the ICF server setup This change also - enabled datalad-style SSH logins/blocking for appveyor - discontinues preparation/test execution via the root-user, unless without alternative - deployes singularity v3 in a fixed version, suitable for the ICF server The singularity image is deposited as a build artifact and is retrievable from https://ci.appveyor.com/api/projects/mih/inm-icf-utilities/artifacts/icf.sif See https://www.appveyor.com/docs/packaging-artifacts/#permalink-to-the-last-successful-build-artifact for details.
11 lines
425 B
Bash
Executable file
11 lines
425 B
Bash
Executable file
#!/bin/bash
|
|
|
|
set -e -u
|
|
|
|
apt-get update -qq
|
|
eatmydata apt-get -y install apache2
|
|
# deploy singularity v2, matching the ICF deployment
|
|
# only download when not already cached
|
|
[ ! -f singularity-container_3.8.7_amd64.deb ] && wget https://github.com/apptainer/singularity/releases/download/v3.8.7/singularity-container_3.8.7_amd64.deb || true
|
|
eatmydata dpkg -i singularity-container_3.8.7_amd64.deb
|
|
eatmydata apt-get install -f
|