add empty site-config dir for lab to make pipelines pass

.gitlab-ci.yml

@@ -6,6 +6,7 @@ variables:
   GITLAB_BUILD_ENV_DOCKER_IMAGE: docker-registry.ebrains.eu/tc/ebrains-spack-build-env/gitlab_runners_nfs:devel
   SPACK_VERSION: v0.19.2
   SPACK_PATH_GITLAB: /mnt/spack_v0.19.2
+  SYSTEMNAME: ebrainslab
 
 # start an OpenShift Job that will build the Spack environment
 .deploy-build-environment:
@@ -197,6 +198,7 @@ build-spack-env-on-runner:
     - spack compiler find
     - spack repo add .
     - spack env create $SPACK_DEV_ENV spack.yaml
+    - cp -r site-config $SPACK_ROOT/var/spack/environments/$SPACK_DEV_ENV/
     - spack env activate $SPACK_DEV_ENV
     - spack install -y -j2 --fresh --test root
   after_script:
@@ -270,8 +272,8 @@ sync-gitlab-spack-instance:
     - spack compiler list
     # activate and update environment (and create it, if it doesn't exist)
     - spack env list | grep -q $SPACK_NFS_ENV && echo "Environment created already" || spack env create $SPACK_NFS_ENV $CI_PROJECT_DIR/spack.yaml
+    - cp -r -t $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/ $CI_PROJECT_DIR/{site-config,spack.yaml}
     - spack env activate $SPACK_NFS_ENV
-    - cp $CI_PROJECT_DIR/spack.yaml $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/spack.yaml
     # There is a known spack bug (https://github.com/spack/spack/issues/29447) in installing test dependencies for installation tests. The workaround suggested
     # in the issue is to NOT concretize separately, but simply remove the .lock file and let the enironment be concretized by the spack install command:
     - rm $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/spack.lock || echo "No spack.lock file"

create_job.sh

@@ -39,6 +39,8 @@ spec:
             mountPath: /srv
         command: ["/usr/local/bin/deploy-build-env.sh", "$OP", "$INSTALLATION_ROOT", "$SPACK_VERSION", "$SPACK_ENV", "$BRANCH", "$RELEASE_NAME", "$LAB_KERNEL_ROOT"]
         env:
+          - name: SYSTEMNAME
+            value: ebrainslab
           - name: GITLAB_USER
             valueFrom:
               secretKeyRef:

install_spack_env.sh

@@ -50,7 +50,7 @@ then
 fi
 
 # update and activate environment
-cp $EBRAINS_REPO/spack.yaml $SPACK_ROOT/var/spack/environments/$EBRAINS_SPACK_ENV/spack.yaml
+cp -r -t $SPACK_ROOT/var/spack/environments/$EBRAINS_SPACK_ENV/ $EBRAINS_REPO/{site-config,spack.yaml}
 spack env activate $EBRAINS_SPACK_ENV
 # There is a known spack bug (https://github.com/spack/spack/issues/29447) in installing test dependencies
 # for installation tests. The workaround suggested in the issue is to NOT concretize separately, but simply