136100f610
All checks were successful
continuous-integration/drone/push Build is passing
WARM_CANONICAL=True added to every recipe in cc-ci-plan/used-recipes.md (20 weekly + uptime-kuma external). enrolled_recipes() now returns all 21. Test fixtures (custom-html-*-bad, concurrency, regression) intentionally left unenrolled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
21 lines
1.1 KiB
Python
21 lines
1.1 KiB
Python
# Per-recipe harness config for drone (CI server with gitea SCM dependency).
|
|
# Drone requires a gitea SCM backend to boot; the harness provisions gitea as an install-time
|
|
# dep, creates an admin user + OAuth2 app in it, and wires DRONE_GITEA_* via install_steps.sh
|
|
# before the single drone deploy. Upgrade tier: viable (1.8.0 → 1.9.0).
|
|
#
|
|
# The backup rung is a structural skip: the drone recipe ships no backupbot labels and abra.sh
|
|
# exports only DRONE_ENV_VERSION (no backup functions). Documented in PARITY.md.
|
|
HEALTH_PATH = "/healthz"
|
|
HEALTH_OK = (200,)
|
|
DEPLOY_TIMEOUT = 600
|
|
HTTP_TIMEOUT = 600
|
|
|
|
# Gitea is deployed as an install-time dep. The orchestrator provisions it before drone, runs
|
|
# install_steps.sh (which wires GITEA_CLIENT_ID + GITEA_DOMAIN + client_secret into drone's env
|
|
# and compose), then deploys drone once with SCM already configured.
|
|
DEPS = ["gitea"]
|
|
|
|
# canon §2.B: enroll as a DATA-WARM canonical (all recipes enrolled — operator 2026-06-17).
|
|
# The weekly sweep promotes this recipe's canonical to its latest green RELEASE TAG.
|
|
WARM_CANONICAL = True
|