create new experimental release

.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"