Skip to content

ci: rebuild the status page hourly during the day - #7

Merged
dhamsey3 merged 1 commit into
mainfrom
ci/status-hourly
Oct 19, 2026
Merged

dhamsey3 merged 1 commit into
mainfrom
ci/status-hourly

Conversation

@dhamsey3

Copy link
Copy Markdown
Owner

The status page has been running hours behind the pipeline. GitHub started both scheduled rebuilds 3 to 4 hours late every day so far: 09:30 UTC ran at about 13:20, and 14:15 at about 17:20. So each morning the page didn't show that day's forecast until early afternoon.

Change

  • status.yml runs at 17 past every hour from 07:17 to 18:17 UTC, 12 runs a day. In both CET and CEST that covers the 09:00 forecast, the 10:15 deadline and 14:30 scoring, including scoring's up to 3 hours of waiting for late prices. With a run every hour, a late start costs about an hour instead of half a day. Minute 17 avoids GitHub's busy top of the hour.
  • The page's intro line, the README and ADR 6 now say "hourly". ADR 6 gets a dated update section rather than a rewrite.

Cost

  • Actions minutes are free on a public repo, and the Budgets API call is free.
  • Each build reads the live scores from S3, and those reads grow with the record: two models' scores per day. After a year, 12 builds a day comes to about 260k S3 GETs a month, roughly $0.11 at Frankfurt prices. Today it's a fraction of a cent.

Tests and lint pass. The status workflow change applies from its next scheduled time after merge.

GitHub started the two scheduled status runs 3 to 4 hours late on every
day so far (09:30 UTC ran at about 13:20, 14:15 at about 17:20). The page
missed each day's forecast for most of the morning.

The workflow now runs hourly from 07:17 to 18:17 UTC. That covers the
09:00 forecast, the 10:15 deadline and 14:30 scoring, including up to 3
hours of waiting for late prices, in both CET and CEST. A late start now
costs about an hour. Minute 17 avoids the busy top of the hour. The page
text, README and ADR 6 (a dated update) say so.
@dhamsey3
dhamsey3 merged commit dfcf2d2 into main Oct 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant