From dc51cd95c6057dccfc1b110530797052f28dee59 Mon Sep 17 00:00:00 2001 From: Athanasios Karmas <karmas@athenarc.gr> Date: Wed, 2 Jun 2021 13:08:38 +0000 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 245a2612..b74e9e99 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ Build and distribute software with Spack ## Bulding software binaries with Spack -**The current build path needs to be automated with CI (e.g. gitlab runners)** +**ToDo: The current build path needs to be automated with CI (e.g. gitlab runners)** - As a reference you can find [here](https://spack.readthedocs.io/en/latest/command_index.html) the Spack commands list - We will need to have different Spack environments to test specs (and build packages) and when tests are passing release specs from testing environments to production environment @@ -46,7 +46,7 @@ https://nest-simulator.readthedocs.io/en/nest-2.20.1/auto_examples/one_neuron.ht ## Delivery of the software binaries -**This methodology will change, and the delivery will be be implemented via Gitlab CI and use of the shared NFS drive** +**ToDo:This methodology will change, and the delivery will be be implemented via Gitlab CI and use of the shared NFS drive** - After build is complete, we move on to zip the **"$SPACK_ROOT"** and the **~/.spack** folders of the build environment and transfer them to CSCS Object Storage (currently, in the future it will be a shared NFS drive) - The artifacts that were built can now be used from the Collaboratory running containers to load and run the available simulation tools -- GitLab