Newer
Older
#BUILD_ENV: ebrains/ for DT
BUILD_ENV: test-build
SWIFT_FILE: ebrains-spack-builds${CI_PIPELINE_ID}.tar.gz
#- 'curl -H "X-Auth-Token: ${OS_TOKEN}" -X DELETE ${OBJSTORE}ebrains-spack-builds.tar.gz'
- tar czf ${SWIFT_FILE} packages/ repo.yaml spack.yaml
- 'curl -H "X-Auth-Token: ${OS_TOKEN}" -i ${OBJSTORE} -X PUT -T ${SWIFT_FILE}'
stage: deploy
before_script:
- oc login "$OPENSHIFT_SERVER" --token="$OPENSHIFT_TOKEN"
script:
# create job description file
- chmod a+x create_job.sh
Athanasios Karmas
committed
- ./create_job.sh $BUILD_ENV $OP $SWIFT_FILE $CI_PIPELINE_ID
- cat simplejob${CI_PIPELINE_ID}.yml
Athanasios Karmas
committed
#- oc delete job simplejob || true
Athanasios Karmas
committed
- oc create -f simplejob${CI_PIPELINE_ID}.yml
# wait for job to finish https://stackoverflow.com/questions/5073453wait-for-kubernetes-job-to-complete-on-either-failure-success-using-command-line
Athanasios Karmas
committed
- oc get job/simplejob${CI_PIPELINE_ID} -o=jsonpath='{.status}' -w && oc get job/simplejob -o=jsonpath='{.status.conditions[*].type}' | grep -i -E 'failed|complete' || echo 'Failed'
- oc logs jobs/simplejob${CI_PIPELINE_ID}