feat(ci): add Print runner wait time step to all workflow jobs #517

Merged
guettlibot merged 1 commits from issue-504-runner-wait-time into main 2026-06-07 00:40:10 +00:00
guettlibot commented 2026-06-07 00:39:58 +00:00 (Migrated from codeberg.org)

Summary

  • Adds a Print runner wait time step as the first step in every CI job across ci.yml, deploy.yml, website.yml, and firebase-tests.yml
  • Records the moment a runner picks up the job (date +%s) and fetches the run's created_at from the Forgejo tasks API to compute queue wait time
  • Uses github.token (no new secrets needed); prints unknown and continues without failing if the API lookup returns nothing

Jobs updated

  • ci.yml: check
  • deploy.yml: check-changes, deploy-playstore, deploy-apk, build-linux, label-deploy-health
  • website.yml: deploy
  • firebase-tests.yml: check-changes, test-android-firebase

Verification

  • All four workflow files reviewed — step is placed before actions/checkout (or before the first step in label-deploy-health which has no checkout)
  • Step is self-contained: never fails the job if the API lookup does not find the run

Closes #504

## Summary - Adds a `Print runner wait time` step as the **first step** in every CI job across `ci.yml`, `deploy.yml`, `website.yml`, and `firebase-tests.yml` - Records the moment a runner picks up the job (`date +%s`) and fetches the run's `created_at` from the Forgejo tasks API to compute queue wait time - Uses `github.token` (no new secrets needed); prints `unknown` and continues without failing if the API lookup returns nothing ## Jobs updated - `ci.yml`: `check` - `deploy.yml`: `check-changes`, `deploy-playstore`, `deploy-apk`, `build-linux`, `label-deploy-health` - `website.yml`: `deploy` - `firebase-tests.yml`: `check-changes`, `test-android-firebase` ## Verification - All four workflow files reviewed — step is placed before `actions/checkout` (or before the first step in `label-deploy-health` which has no checkout) - Step is self-contained: never fails the job if the API lookup does not find the run Closes #504
Sign in to join this conversation.