pat-s
56d26ef59c
All checks were successful
ci/crow/cron/build/1 Pipeline was successful
ci/crow/cron/build/3 Pipeline was successful
ci/crow/cron/build/5 Pipeline was successful
ci/crow/cron/build/7 Pipeline was successful
ci/crow/cron/build/9 Pipeline was successful
ci/crow/cron/build/10 Pipeline was successful
ci/crow/cron/build/11 Pipeline was successful
ci/crow/cron/build/12 Pipeline was successful
ci/crow/cron/build/14 Pipeline was successful
ci/crow/cron/build/15 Pipeline was successful
ci/crow/cron/build/16 Pipeline was successful
ci/crow/cron/build/17 Pipeline was successful
ci/crow/cron/build/18 Pipeline was successful
ci/crow/cron/build/4 Pipeline was successful
ci/crow/cron/build/6 Pipeline was successful
ci/crow/cron/build/2 Pipeline was successful
ci/crow/cron/build/13 Pipeline was successful
ci/crow/cron/build/8 Pipeline was successful
13 lines
705 B
Markdown
13 lines
705 B
Markdown
# CLAUDE.md
|
|
|
|
CI pipelines (Crow, in `.crow/`) that build R binaries and upload them to Backblaze B2.
|
|
|
|
## Conventions
|
|
|
|
- **PRs:** the remote is Forgejo on `git.devxy.io`; use `fj -H git.devxy.io` (not `gh`).
|
|
- **Storage:** Backblaze B2 bucket `devxy-r-builds` (endpoint configured in `.crow/build.yaml`).
|
|
|
|
## Gotchas
|
|
|
|
- **B2 requires authentication for the list-bucket API.** Anonymous GET only works for individual public-read objects — an empty bucket listing usually means missing credentials, not an empty bucket. This silently broke rebuild dedup once.
|
|
- When a pipeline fails, fetch the Crow logs yourself instead of asking the user to paste them, and monitor reruns in the background until green.
|