From 884f7774605794ee92c67afdac143d518f5dfc26 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wolfgang=20Hu=C3=9F?= Date: Wed, 20 Jul 2022 09:26:11 +0200 Subject: [PATCH] Change order of deployments and the timeout to wait for in 'publish.yml' --- .github/workflows/publish.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index d2c20e352..0c2a69f24 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -302,10 +302,10 @@ jobs: kubectl -n default rollout restart deployment/ocelot-neo4j - name: Verify deployment and wait for the pods of each deplyment to get ready for cleaning and seeding of the database run: | - kubectl -n default rollout status deployment/ocelot-webapp --timeout=240s - kubectl -n default rollout status deployment/ocelot-maintenance --timeout=240s - kubectl -n default rollout status deployment/ocelot-backend --timeout=240s - kubectl -n default rollout status deployment/ocelot-neo4j --timeout=240s + kubectl -n default rollout status deployment/ocelot-backend --timeout=400s + kubectl -n default rollout status deployment/ocelot-neo4j --timeout=400s + kubectl -n default rollout status deployment/ocelot-maintenance --timeout=400s + kubectl -n default rollout status deployment/ocelot-webapp --timeout=400s - name: Reset and seed Neo4j database via backend for staging # db cleaning and seeding is only possible in production if env 'PRODUCTION_DB_CLEAN_ALLOW=true' is set in deployment run: |