|
|
|
[Continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) (CI) considers the current state of the project and can perform tests and checks on the full code base.
|
|
|
|
|
|
|
|
How to setup CI in [Gitlab](https://docs.gitlab.com/ee/ci/quick_start/index.html) or [Github](https://docs.github.com/en/actions/automating-builds-and-tests/about-continuous-integration).
|
|
|
|
|
|
|
|
You can use the CI to
|
|
|
|
- [run pre-commit](Git/pre-commit)
|
|
|
|
- run unit tests or benchmarks
|
|
|
|
- [compile your code](Tools/Compiling-and-build-setups-for-C-and-C++)
|
|
|
|
|
|
|
|
The CI can be run
|
|
|
|
- on every commit
|
|
|
|
- upon merging a branch
|
|
|
|
- upon pressing a button
|
|
|
|
- ...
|
|
|
|
|
|
|
|
Using a CI is beneficial to automatize checks. |
|
|
\ No newline at end of file |
