|
|
# Description of Setup
|
|
|
|
|
|
The main gitlab server to develop CORSIKA 8 is gitlab.ikp.kit.edu
|
|
|
|
|
|
It is configured to run CI jobs for all pushes and merge requests. The configuration can be found in the repository's **.gitlab-ci.yml**
|
... | ... | @@ -6,7 +8,7 @@ The jobs are based on docker containers published here ```https://hub.docker.com |
|
|
|
|
|
The CI jobs are distributed on Runners via the ```corsika``` **tag**. Runners need to support **docker**.
|
|
|
|
|
|
Note, we setup our Runners to be **assigned** to the corsika and related projects (group runners for https://gitlab.ikp.kit.edu/AirShowerPhysics). This also means: from your personal fork you might not be able to run CI jobs on the Runners. Thus, it is an advantage to keep main development on the main corsika repository.
|
|
|
Note, we setup our Runners to be **assigned** to the corsika and related projects (group runners for https://gitlab.ikp.kit.edu/AirShowerPhysics, token: sDrYV8raCVzKRk7vyn2v). This also means: from your personal fork you might not be able to run CI jobs on the Runners. Thus, it is an advantage to keep main development on the main corsika repository.
|
|
|
|
|
|
## General setup of Runners
|
|
|
|
... | ... | @@ -26,11 +28,9 @@ The following configurations are needed (config.toml): |
|
|
[runners.custom_build_dir]
|
|
|
enabled = true
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Here are some commands used to setup Runners on ```augerbot```:
|
|
|
## Here are commands used to setup Runners on ```augerbot```:
|
|
|
|
|
|
Note: This is not the best way to setup runners, we prefer that it is better to use containers to start runners!
|
|
|
|
... | ... | @@ -39,7 +39,10 @@ Note: This is not the best way to setup runners, we prefer that it is better to |
|
|
- start service
|
|
|
``` sudo gitlab-runner run --working-directory ~ --config /etc/gitlab-runner/config.toml --service gitlab-runner --syslog --user gitlab-runner```
|
|
|
|
|
|
## Observed problems
|
|
|
## Here is how the UNAM Runners are setup
|
|
|
|
|
|
|
|
|
## Observed problems, Troubleshooting
|
|
|
|
|
|
If the Runners using docker get stuck periodically (this seems not to happen any more with recent runner versions!). It seems this is most likely related to (stale?) docker images and missing cleanup. We developed the following script which so far works to get Runners back online:
|
|
|
|
... | ... | |