Differences

This shows you the differences between two versions of the page.

--- services:gitlab:gitlab-runner [2021/05/19 09:47] – hoffmac00
+++ services:gitlab:gitlab-runner [2022/07/08 15:58] (current) – hoffmac00
@@ Line 1: / Line 1: @@
-====== Shared GitLab Runner of the Physics Department ======
+====== Shared GitLab Runners of the Physics Department ======
 All repositories have the ability to use the shared GitLab Runners. They can be used to compile, test and deliver code automatically. They must not be used for numerical computations.
@@ Line 121: / Line 121: @@
 ===== Parallel and matrix =====
-Inside a job, you can use ''%%parallel%%'' to run it multiple times simultaneously. Some languages, e.g. ruby also have the ability to split tests across these parallel jobs.
+Inside a job, you can use ''%%parallel%%'' to run it multiple times simultaneously. Some languages, e.g. ruby also have the ability to split tests across these parallel jobs.
 <code yaml>
@@ Line 193: / Line 193: @@
 will use the checksum of ''%%requirements.txt%%'' as the key. This means your cache only has to be recreated when ''%%requirements.txt%%'' changes.
-Jobs that update the cache should always be idempotent (i.e. should not change anything when run again) and reuse existing files. This means you wouldn’t need to reinstall, say 2GiB in a python venv with every run of a pipeline but only update the existing modules.
+Jobs that update the cache should always be idempotent (i.e. should not change anything when run again) and reuse existing files. This means you wouldn’t need to reinstall, say 2GiB in a python venv with every run of a pipeline but only update the existing modules.
 ===== Images =====
@@ Line 199: / Line 199: @@
 GitLab CI allows for choosing images. All available images are based on debian. There are multiple variants and multiple releases available.
-Available releases: * buster * bullseye * sid * stable (stable release, installed on workstations) * testing (next stable release)
+Available releases:
+  * buster
+  * bullseye
+  * bookworm (julia is not packaged for this release currently, therefore the julia variant is not available)
+  * oldstable (last stable release)
+  * stable (stable release, installed on workstations)
+  * testing (next stable release)
 These releases correspond to the debian codenames.
-Available variants: * base (most simple variant e.g. for simple shell scripts) * dev (for C/C++ projects) * python (comes with the same python libs as the workstations) * tex (comes with the same TeX packages as the workstations) * fortran (comes with gfortran) * haskell (comes with ghc) * julia (comes with julia) * ruby (comes with ruby) * deb (for debian packaging) * full (Includes everything from above and is close to the workstation configuration)
+Available variants:
+  * base (most simple variant e.g. for simple shell scripts)
+  * dev (for C/C++ projects)
+  * python (comes with the same python libs as the workstations)
+  * tex (comes with the same TeX packages as the workstations)
+  * fortran (comes with gfortran)
+  * haskell (comes with ghc)
+  * julia (comes with julia)
+  * ruby (comes with ruby)
+  * deb (for debian packaging)
+  * full (Includes everything from above and is close to the workstation configuration)
 Launch time increases with the size of the image which is why the full variant will be slowest to start.
@@ Line 210: / Line 226: @@
 <code yaml>
-image: buster-python
+image: bullseye-python
 </code>
@@ Line 216: / Line 232: @@
 <code yaml>
-image: buster-python
+image: bullseye-python
 ...
 deploy:
-    image: buster-base
+    image: bullseye-base
     script:
         - ./deploy.sh
 </code>
-This will use ''%%buster-python%%'' for all jobs, except ''%%deploy%%'', which will use the minimal base image.
+This will use ''%%bullseye-python%%'' for all jobs, except ''%%deploy%%'', which will use the minimal base image.
 ===== Notes on Resource Usage =====