From 8186b3e6de0b0d4012b4b556b329037368764a1f Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Fri, 1 Nov 2024 12:48:35 +0100
Subject: [PATCH] Update cicd.md

---
 docs.it4i/general/tools/cicd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs.it4i/general/tools/cicd.md b/docs.it4i/general/tools/cicd.md
index 9520925d..93311c01 100644
--- a/docs.it4i/general/tools/cicd.md
+++ b/docs.it4i/general/tools/cicd.md
@@ -22,7 +22,7 @@ For more information about the Jacamar CI driver, please visit [the official doc
 
 The execution of CI pipelines works as follows. First, a user in the IT4I GitLab server triggers a CI pipeline (for example, by making push to a repository, etc.). Then, the jobs, which the pipeline consists of, are sent to the corresponding runner, running in the login node. Lastly, for every CI job, the runner clones the repository (or just fetches changes to an already cloned one, if there are any) and submits the job as a Slurm job to the corresponding HPC cluster using the `sbatch` command. After each execution of a job, the runner reports the results back to the server and uploads the artifacts (if specified).
 
-<img src="../../img/it4i-ci.png" title="IT4I CI" width="750">
+<img src="../../../img/it4i-ci.png" title="IT4I CI" width="750">
 
 !!! note
     The GitLab runners at Karolina and Barbora are able to submit (as a Slurm job) and execute 32 CI jobs concurrently, while the runner at Complementary systems can submit 16 jobs concurrently at most. Jobs above this limit are postponed in submission to respective slurm queue until a previous job has finished.
-- 
GitLab