The last two `deploy` Actions failed with a timeout on the `build` stage

google / slo-generator

SLO Generator computes SLIs, SLOs, Error Budgets and Burn Rates from supported backends, then exports an SLO report to supported targets.

Apache License 2.0

489 stars 78 forks source link

The last two `deploy` Actions failed with a timeout on the `build` stage #272

Closed lvaylet closed 2 years ago

lvaylet commented 2 years ago

Upon investigating the Cloud Build history, these timeouts are due to the larger number of checks (linting, types, vulnerabilities) added in #267. The last two builds took 9m51s and 11m25s, respectively, while the GitHub Action is configured to time out after 10 minutes.

Increase the timeout from 10 minutes to 15 minutes in .github/workflows/deploy.yaml?