From 993a6b65c12a6d6054f436eb206ddb279e1eb50d Mon Sep 17 00:00:00 2001 From: Jan Siwiec <jan.siwiec@vsb.cz> Date: Wed, 13 Nov 2024 07:43:31 +0100 Subject: [PATCH] Update cicd.md --- docs.it4i/general/tools/cicd.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs.it4i/general/tools/cicd.md b/docs.it4i/general/tools/cicd.md index 6d61760b..9a13e6aa 100644 --- a/docs.it4i/general/tools/cicd.md +++ b/docs.it4i/general/tools/cicd.md @@ -14,7 +14,7 @@ IT4Innovations maintains a GitLab server (code.it4i.cz), which has built-in supp Detailed documentation about GitLab CI/CD is available [here][1]. -### Karolina, Barbora, and Complementary systems +### Karolina, Barbora, and Complementary Systems For all the users, a unified solution is provided to let them execute their CI jobs at Karolina, Barbora, and Complementary systems without the need to create their own project runners. For each of the HPC clusters, a GitLab instance runner has been deployed. The runners are running in the login nodes and are visible to all the projects of the IT4I GitLab server. These runners are shared by all users. @@ -44,7 +44,7 @@ To begin with, a CI pipeline of a project must be defined in a YAML file. The mo !!! note The default maximum time that a CI job can run for before it times out is 1 hour. This can be changed in [project's CI/CD settings][9]. When jobs exceed the specified timeout, they are marked as failed. Pending jobs are dropped after 24 hours of inactivity. -### Execution of CI Pipelines at the HPC clusters +### Execution of CI Pipelines at the HPC Clusters Every CI job in the project CI pipeline, intended to be submitted as a Slurm job to one of the HPC clusters, must have the 3 following keywords specified in its definition. -- GitLab