From 29c1b3dc351fec27271cd99207b12a7af6cc685d Mon Sep 17 00:00:00 2001
From: Lukas Werner <lks.werner@fau.de>
Date: Mon, 16 Aug 2021 07:47:56 +0000
Subject: [PATCH] Update README.md

---
 documentation/README.md | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/documentation/README.md b/documentation/README.md
index 6ed3716..6f32241 100644
--- a/documentation/README.md
+++ b/documentation/README.md
@@ -24,6 +24,8 @@ Together with the public key being deposited on the cluster, this will ensure pr
 In this file, we configure options for the SLURM submission on the test cluster.
 A example config can be found in `example.gitlab-ci.yml`.
 
+Each job needs to have the tag `testcluster`.
+
 SLURM options can be set either globally in the `variables` section, or on a per-job basis.
 The latter will override global variables with the same name.
 
@@ -32,15 +34,23 @@ variables:
 	SLURM_NODELIST: "phinally"
 	SLURM_TIMELIMIT: "30"
 
+...
+build:
+	script:
+		- make
+	tags:
+		- testcluster
+
 ...
 benchmark-broadep2:
 	variables:
 		SLURM_NODELIST: "broadep2" # uses broadep2 instead of phinally for this benchmark
 		SLURM_TIMELIMIT: "10" # limit time to 10 instead of 30 minutes
-
+	tags:
+		- testcluster
 ```
 
-This configuration already suffices to have the CI jobs running on the node `phinally`.
+This configuration already suffices to have the CI jobs running on the node `phinally`, with `benchmark-broadep2` being executed on `broadep2`.
 With "phinally" being the default node and time limit by default at 120, even having no configuration at all would work just fine.
 
 To pick a node to run your job on, set `SLURM_NODELIST` to the nodes hostname.
-- 
GitLab