CI pipeline for mysql unit tests

Summary

The pipeline should also run the tests with a MySQL as backend server. This MR implements this.

See also #33 (closed).

Focus

• Does the MySQL pipeline fail at the expected point?
• Is outsourcing pipeline code to a Makefile a reasonable step to prevent redundancy in the scripts?

Test Environment

Just watch the pipeline run.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

.gitlab-ci.yml

@@ -21,6 +21,7 @@
 
 services:
   - mariadb:10.4
+  - mysql:8.0
 variables:
   DEPLOY_REF: dev
   CI_REGISTRY_IMAGE: $CI_REGISTRY/caosdb/src/caosdb-mysqlbackend/testenv:latest
@@ -62,7 +63,7 @@ unittests:
     - cp config.defaults .config
     - echo 'DATABASE_USER_HOST_LIST="%,"' >> .config
     - echo "MYSQL_USER_PASSWORD=$MYSQL_ROOT_PASSWORD" >> .config
-    - echo "MYSQL_HOST=mariadb" >> .config
+    - echo "MYSQL_HOST=mysql" >> .config
     - sleep 10
     - make install
     - ./utils/make_db restore_db tests/example.dump.sql