Update CI CD with Gitlab authored by Matthias Taeschner's avatar Matthias Taeschner
# General information
We use continuous development methodologies provided by [GitLab CI/CD](https://docs.gitlab.com/ee/ci/).
We use continuous development methodologies provided by [GitLab CI/CD](https://docs.gitlab.com/ee/ci/). A GitLab Runner is required to execute the corresponding pipelines. We provide the runner via a virtual machine, hosted at `scads-ci.sc.uni-leipzig.de`. The VM is managed by Lars-Peter and @matthias.taeschner.
The runner is executed via a docker container - more information can be found [here](https://docs.gitlab.com/runner/install/docker.html). Please note that all files created in a dockerized pipeline will be deleted when the Docker-Container is shut down afterwards and therefore require special treatment if they are to be persisted.
# Configuration of the CI/CD process
## Configuration of the CI/CD process
CI/CD pipelines are configured with the [gitlab-ci.yml](https://git.informatik.uni-leipzig.de/dbs/FAMER/-/blob/master/.gitlab-ci.yml) After a push to the repository, the build process with the specified phases is triggered. Maven is used for building with the following parameters:
- `--batch-mode` Run in non-interactive (batch) mode, Maven will never stop to accept input from the user.
......
......