Update Continuous Integration and Continuous Deployment authored by Fabian Nuraddin Alexander Gabel's avatar Fabian Nuraddin Alexander Gabel
...@@ -80,18 +80,17 @@ Overall the pipeline features 5 Stages: ...@@ -80,18 +80,17 @@ Overall the pipeline features 5 Stages:
![](https://writemd.rz.tuhh.de/uploads/upload_f51cd45c68f0e95122226310a9d4834d.gif) ![](https://writemd.rz.tuhh.de/uploads/upload_f51cd45c68f0e95122226310a9d4834d.gif)
The first two stages are testing stages: The first two stages are testing stages:
* [`docker-update`](): checks, whether the docker images from the repository's [container registry](https://collaborating.tuhh.de/cfg0846/research-topics-mat-tuhh/container_registry) are available and rebuilds them if the `Dockerfile`s have changed * [`docker-update`](#docker-update): checks, whether the docker images from the repository's [container registry](https://collaborating.tuhh.de/cfg0846/research-topics-mat-tuhh/container_registry) are available and rebuilds them if the `Dockerfile`s have changed
* `testing`: performs various tests of the [preprocessor](Preprocessors) and [building]() routines * [`testing`](#testing): performs various tests of the [preprocessor](Preprocessors) and [building]() routines
* `build`: constructs the various products like standalone webpages, and TUHH-delivery packages * [`build`](#build): constructs the various products like standalone webpages, and TUHH-delivery packages
* `review`: starts the review apps for the merge request * [`review`](#review): starts the review apps for the merge request
* `deploy`: ships the products to their final destination (`www3`, `www3-dev`, `mat`) * [`deploy`](#deploy): ships the products to their final destination (`www3`, `www3-dev`, `mat`)
#### `docker-update` #### `docker-update`
Here, all [Docker](/Dependencies#docker) images are updated. Here, all [Docker](/Dependencies#docker) images are updated.
#### `testing #### `testing`
The testing stage consists of the following functionality tests: Each time a bash-script with prefix `test_` is executed. All scripts reside in `/bin` and exit with exit code `1` if something goes wrong. In case of a failing test, subsequent states of the pipeline stall. The testing stage consists of the following functionality tests: Each time a bash-script with prefix `test_` is executed. All scripts reside in `/bin` and exit with exit code `1` if something goes wrong. In case of a failing test, subsequent states of the pipeline stall.
Check the code documentation provided by the scripts for further information. Check the code documentation provided by the scripts for further information.
... ...
......