| Filename | Latest commit message | Latest commit date |
|---|---|---|
pat-s
ca336c2720
Some checks failed
ci/crow/cron/build/1 Pipeline failed
ci/crow/cron/build/3 Pipeline was canceled
ci/crow/cron/build/4 Pipeline was canceled
ci/crow/cron/build/12 Pipeline was canceled
ci/crow/cron/build/5 Pipeline was canceled
ci/crow/cron/build/14 Pipeline was canceled
ci/crow/cron/build/6 Pipeline was canceled
ci/crow/cron/build/2 Pipeline was canceled
ci/crow/cron/build/13 Pipeline was canceled
ci/crow/cron/build/17 Pipeline was canceled
ci/crow/cron/build/18 Pipeline was canceled
ci/crow/cron/build/9 Pipeline was canceled
ci/crow/cron/build/16 Pipeline was canceled
ci/crow/cron/build/10 Pipeline was canceled
ci/crow/cron/build/11 Pipeline was canceled
ci/crow/cron/build/7 Pipeline was canceled
ci/crow/cron/build/8 Pipeline was canceled
ci/crow/cron/build/15 Pipeline was canceled
The existing-version check listed the bucket with an anonymous curl, but
Backblaze B2 requires authentication for the list-bucket API, so it returned
AccessDenied and r-versions-existing.txt was always empty -> every version
was rebuilt despite already existing in s3.
Signing the request is not workable here: the B2 credentials are scoped to
the plugin-s3 image in crow and are not injected into this plain alpine step
(curl saw --user ":").
Individual artifacts are public-read, so probe each expected object URL with
an anonymous HEAD instead of listing the bucket. The filename mirrors what
nfpm produces (version/release pinned to 1): r-<ver>_1_<arch>.{apk,deb} for
alpine/ubuntu and R-<ver>-1-1.<arch>.rpm for el*. Verified against the live
bucket for all three packager families.
Reviewed-on: #8
|
||
| .. | ||
| build.yaml | ||