...
The CI/CD pipeline has to be specified inside the .gitlab-ci.yml
file through tags (see Gitlab documentation for how to create and manage pipelines).
ImportantIMPORTANT: There are two different kind of runners. You can select them by specifying one or more tags in order have to identify which runner you would like to run your pipeline by specifying one or more tags summarized in the table at the bottom of the page.
ImportantIMPORTANT: If you do not select any tag, the pipeline will never start.
...
2 CPU-only runners, with access up to 16 CPUs each. Jobs are executed in concurrent execution. (specific tags: ppc64le, cpu, podman)
4 CPU+GPU runners, limited to run 1 CI job each at the time. Each runner has access to a dedicated GPU. No concurrent execution is allowed on these runners. (specific tags: ppc64le, podman, nvidia-volta)
Summary
Below we summarize the runners and the tags needed to select the correct one.
Cluster | Runners | Tags | Notes |
---|---|---|---|
Galileo100 | 2 CPU-only | x86_64 | Up to 24 cpus each. Concurrent execution |
2 CPU+GPU | x86_64 | Each runner has a dedicated GPU. No concurrent execution | |
Marconi100 | 2 CPU-only | ppc64le | Up to 16 cpus each. |
4 CPU+GPU | ppc64le | Each runner has a dedicated GPU. |
IMPORTANT: If you do not select any tag, the pipeline will never start.