Introducing healthcheck to reduce latency issues with different availabilities of wordpress

Author: ArneTR

energy-tests/compose.yml

@@ -14,6 +14,14 @@ services:
       - MYSQL_PASSWORD=wordpress
     expose:
       - 3306
+    healthcheck:
+      test: [
+        "CMD", "bash", "-c", "mysqladmin ping -h localhost -u wordpress -pwordpress | grep \"mysqld is alive\""
+      ]
+      interval: "1h" # effectively turns repeated healthchecks during runtime off
+      start_period: "60s"
+      start_interval: "1s"
+
   gcb-wordpress-apache:
     build:
       context: .
@@ -31,5 +39,6 @@ services:
       - WORDPRESS_DB_PASSWORD=wordpress
       - WORDPRESS_DB_NAME=wordpress
     depends_on:
-      - gcb-wordpress-mariadb
+      gcb-wordpress-mariadb:
+        condition: service_healthy
 

energy-tests/usage_scenario.yml

@@ -29,6 +29,9 @@ services:
       - cp /tmp/repo/energy-tests/puppeteer-flow.js /var/www/puppeteer-flow.js
     networks:
       - gcb-wordpress-mariadb-network
+    depends_on:
+      gcb-wordpress-mariadb:
+        condition: service_healthy
 
 flow:
   - name: Check Website