fix(ci): revert deploy-staging and staging-e2e runner back to saas
CI/CD Pipeline / Staging E2E Tests (push) Has been skipped
CI/CD Pipeline / Build Production Runtime Images (push) Has been skipped
CI/CD Pipeline / Deploy Production (push) Has been skipped
CI/CD Pipeline / Production Browser E2E (push) Has been skipped
CI/CD Pipeline / Build & Push Staging (Watchtower auto-deploy) (push) Failing after 26h50m6s
CI/CD Pipeline / Frontend Lint (push) Failing after 26h51m4s
CI/CD Pipeline / Validate Code Quality And Tests (push) Failing after 26h51m4s
CI/CD Pipeline / Staging E2E Tests (push) Has been skipped
CI/CD Pipeline / Build Production Runtime Images (push) Has been skipped
CI/CD Pipeline / Deploy Production (push) Has been skipped
CI/CD Pipeline / Production Browser E2E (push) Has been skipped
CI/CD Pipeline / Build & Push Staging (Watchtower auto-deploy) (push) Failing after 26h50m6s
CI/CD Pipeline / Frontend Lint (push) Failing after 26h51m4s
CI/CD Pipeline / Validate Code Quality And Tests (push) Failing after 26h51m4s
ubuntu-latest does not have Docker installed, causing deploy-staging to fail. The saas runner is now back online (production jobs succeeded on it).
This commit is contained in:
@@ -399,7 +399,7 @@ jobs:
|
||||
|
||||
staging-e2e:
|
||||
name: Staging E2E Tests
|
||||
runs-on: ubuntu-latest
|
||||
runs-on: saas
|
||||
if: github.ref_name == 'develop' || github.ref_name == 'main'
|
||||
needs: deploy-staging
|
||||
|
||||
|
||||
Reference in New Issue
Block a user