fix(cdn): purge the staging zone too #181

Merged

pat-s merged 1 commit from fix/purge-staging-zone into main

2026-08-31 10:31:35 +00:00

pat-s commented

2026-08-31 10:28:11 +00:00

Owner

Motivation

cran-rpkgs-test was added as a second pull zone on the same B2 origin, but it was never added to BUNNY_PULLZONES. It therefore keeps serving pre-reindex indexes behind the same ~370 day cache_expiration_time as production, and nothing ever refreshes it.

That is not cosmetic. The zone exists to be measured, and a verification run against it measures whatever the edge still holds:

production: regressions=0    AGHmatrix Path=NA   Built=R 4.5.3; x86_64-pc
staging   : regressions=161  AGHmatrix Path=4.5  Built=(none)

Same objects, same origin, 161 phantom regressions. I chased that number through two wrong diagnoses before noticing production and staging disagreed.

Change

Add cran-rpkgs-test.b-cdn.net to the purge list in both reindex pipelines.

Note

A Cache-Control: no-cache request header is not a substitute. It was added to the verification script and did not clear this: bunny does not honour it for these objects. Purging is the mechanism that works.

## Motivation `cran-rpkgs-test` was added as a second pull zone on the same B2 origin, but it was never added to `BUNNY_PULLZONES`. It therefore keeps serving pre-reindex indexes behind the same ~370 day `cache_expiration_time` as production, and nothing ever refreshes it. That is not cosmetic. The zone exists to be measured, and a verification run against it measures whatever the edge still holds: ``` production: regressions=0 AGHmatrix Path=NA Built=R 4.5.3; x86_64-pc staging : regressions=161 AGHmatrix Path=4.5 Built=(none) ``` Same objects, same origin, 161 phantom regressions. I chased that number through two wrong diagnoses before noticing production and staging disagreed. ## Change Add `cran-rpkgs-test.b-cdn.net` to the purge list in both reindex pipelines. ## Note A `Cache-Control: no-cache` request header is not a substitute. It was added to the verification script and did **not** clear this: bunny does not honour it for these objects. Purging is the mechanism that works.

pat-s added 1 commit

2026-08-31 10:28:11 +00:00

fix(cdn): purge the staging zone too 996e690985

cran-rpkgs-test was added as a second pull zone on the same B2 origin but
never added to the purge list, so it kept serving pre-reindex indexes
behind the same ~370 day cache_expiration_time as production.

That is not cosmetic: a verification run against staging measures whatever
the edge still holds. amd64/alpine323 reported 161 regressions there while
production, freshly purged, reported zero for the same objects. The
staging zone exists to be measured, so it has to be purged like any other.

pat-s merged commit a2923bf063 into main

2026-08-31 10:31:35 +00:00

pat-s deleted branch fix/purge-staging-zone

2026-08-31 10:31:36 +00:00

pat-s referenced this pull request from a commit

2026-08-31 10:31:36 +00:00

fix(cdn): purge the staging zone too (#181)