You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/services/cicd.md
+45-44Lines changed: 45 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,50 +244,6 @@ It also can give you background for inquiring if and when something in the proce
244
244
1. If the repository uses git submodules, `GIT_SUBMODULE_STRATEGY: recursive` has to be specified (see [GitLab documentation](https://docs.gitlab.com/ee/ci/git_submodules.html#use-git-submodules-in-cicd-jobs))
245
245
1. The [container-builder](#container-builder), which has as input a Dockerfile (specified in the variable `DOCKERFILE`), will take this Dockerfile and execute something similar to `docker build -f $DOCKERFILE .`, where the [build context](#build-context) is the whole (recursively) cloned repository
246
246
247
-
## CI variables
248
-
249
-
Many variables exist during a pipeline run, they are documented at [Gitlab's predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html).
250
-
Variables are exposed as environment variables during job execution, where the key is the environment variable's name.
251
-
Additionally to CI variables available through Gitlab, there are a few CSCS specific variables:
252
-
253
-
### `CSCS_REGISTRY`
254
-
value: `jfrog.svc.cscs.ch`
255
-
256
-
CSCS internal registry, preferred registry to store your container images
The prefix path in the CSCS internal container image registry, to which your pipeline has write access.
262
-
Within this prefix, you can choose any directory structure.
263
-
Images that are pushed to a path matching **/public/** , can be pulled by anybody within CSCS network
264
-
265
-
### `CSCS_CI_MW_URL`
266
-
value: `https://cicd-ext-mw.cscs.ch/ci`
267
-
268
-
The URL of the middleware, the orchestrator software
269
-
270
-
### `CSCS_CI_DEFAULT_SLURM_ACCOUNT`
271
-
value: Configured on the CI setup page in the admin section `Firecrest Slurm Account`
272
-
273
-
The project to which Slurm accounting will go to by default.
274
-
It can be overwritten via `SLURM_ACCOUNT` for individual jobs.
275
-
276
-
### `CSCS_CI_ORIG_CLONE_URL`
277
-
value:
278
-
279
-
* public repositories: HTTPS clone URL, e.g. `https://github.com/my-org/my-project`
280
-
* private repositories: SSH clone URL, e.g. `[email protected]:my-org/my-project`
281
-
282
-
Clone URL for git.
283
-
This is needed for some implementation details of the gitlab-runner custom executor.
284
-
This is the clone URL of the registered project, i.e. this is not the clone URL of the mirror project.
285
-
286
-
### `ARCH`
287
-
value: `x86_64`or `aarch64`
288
-
289
-
This is the architecture of the runner. It is either an ARM64 machine, i.e. `aarch64`, or a traditinal `x86_64` machine.
290
-
291
247
## Containerized CI - best practices
292
248
### Multi-architecture images
293
249
@@ -785,6 +741,51 @@ Below are known differences:
785
741
pipeline_variables: true
786
742
```
787
743
744
+
## CI variables
745
+
746
+
Many variables exist during a pipeline run, they are documented at [Gitlab's predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html).
747
+
Variables are exposed as environment variables during job execution, where the key is the environment variable's name.
748
+
Additionally to CI variables available through Gitlab, there are a few CSCS specific variables:
749
+
750
+
### `CSCS_REGISTRY`
751
+
value: `jfrog.svc.cscs.ch`
752
+
753
+
CSCS internal registry, preferred registry to store your container images
0 commit comments