services:gitlab:gitlab-runner
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
services:gitlab:gitlab-runner [2021/05/19 10:00] – hoffmac00 | services:gitlab:gitlab-runner [2021/08/25 09:57] – hoffmac00 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Shared GitLab | + | ====== Shared GitLab |
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. | 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. | ||
- | ===== Intro into GitLab CI (Continuous Integration) ===== | + | ===== Intro to GitLab CI (Continuous Integration) ===== |
If CI is enabled and there is a push event, GitLab will automatically start a pipeline. A pipeline will run a series of specified jobs on the code and report errors it encounters. Using pipelines, you can see if a change causes an issue with existing code and you can test it for different environments. This works for all branches as well as merge requests or on a schedule. | If CI is enabled and there is a push event, GitLab will automatically start a pipeline. A pipeline will run a series of specified jobs on the code and report errors it encounters. Using pipelines, you can see if a change causes an issue with existing code and you can test it for different environments. This works for all branches as well as merge requests or on a schedule. | ||
Line 27: | Line 27: | ||
</ | </ | ||
- | This will define a job called **test** and in that job it will run '' | + | This will define a job called **test** and in that job it will run '' |
- | Often you want to store the results of a job, for example to use it in further jobs. For this, you can use // | + | Often you will want to store the results of a job, for example to use it in further jobs. For this, you can use // |
<code yaml> | <code yaml> | ||
Line 202: | Line 202: | ||
* buster | * buster | ||
* bullseye | * bullseye | ||
- | * sid | + | * bookworm |
+ | * oldstable (last stable release) | ||
* stable (stable release, installed on workstations) | * stable (stable release, installed on workstations) | ||
* testing (next stable release) | * testing (next stable release) | ||
Line 209: | Line 210: | ||
Available variants: | Available variants: | ||
- | * base (simplest | + | * base (most simple |
* dev (for C/C++ projects) | * dev (for C/C++ projects) | ||
* python (comes with the same python libs as the workstations) | * python (comes with the same python libs as the workstations) | ||
Line 225: | Line 226: | ||
<code yaml> | <code yaml> | ||
- | image: | + | image: |
</ | </ | ||
Line 231: | Line 232: | ||
<code yaml> | <code yaml> | ||
- | image: | + | image: |
... | ... | ||
deploy: | deploy: | ||
- | image: | + | image: |
script: | script: | ||
- ./deploy.sh | - ./deploy.sh | ||
</ | </ | ||
- | This will use '' | + | This will use '' |
===== Notes on Resource Usage ===== | ===== Notes on Resource Usage ===== |
services/gitlab/gitlab-runner.txt · Last modified: 2022/07/08 15:58 by hoffmac00