Files
cc-ci/machine-docs/STATUS-drone.md
autonomic-bot 75c46ac5c1
Some checks failed
continuous-integration/drone/push Build is failing
chore(drone): update STATUS-drone.md — M1 DoD almost done, run 5 in flight
All implementation items checked. Run 5 (DG4.1 fix applied) in flight on cc-ci.
ADV-drone-01 fix verified by Adversary. DG4.1 deploy-count fix explained and committed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-11 22:02:08 +00:00

1.8 KiB

STATUS — phase drone (drone enrollment with gitea SCM dep)

Phase plan: /srv/cc-ci/cc-ci-plan/plan-phase-drone-enroll.md Builder: autonomic-bot / Claude (Builder loop) Started: 2026-06-11T21:30Z


Current state

P0 prerequisite: VERIFIED — /etc/timezone exists (content UTC) on cc-ci host.

Gate M1: IN PROGRESS — harness run 5 in flight (PID 2109869, log /tmp/drone-m1-run5.log on cc-ci)


DoD tracker (M1)

  • P0 verified on host — /etc/timezone = UTC
  • tests/gitea/recipe_meta.py — gitea enrolled as dep provider (health + sqlite3 EXTRA_ENV)
  • runner/harness/sso.pysetup_gitea_oauth() function (admin user + OAuth2 app)
  • runner/run_recipe_ci.py_enrich_deps_with_sso extended for gitea
  • tests/drone/recipe_meta.py — drone with DEPS=["gitea"], health/timeouts
  • tests/drone/install_steps.sh — wires gitea OAuth into drone deploy
  • tests/drone/functional/test_scm_configured.py — no-follow redirect; ADV-drone-01 fixed 7e7e84d
  • tests/drone/PARITY.md — backup structural-skip justification documented
  • Unit tests — 10/10 PASS cold (test_gitea_dep.py)
  • No gate weakening; declared skips justified (backup structural skip per PARITY.md)
  • Harness run green — run 5 in flight (DG4.1 fix 5384f5c)

Fixes applied (M1 path)

  • ADV-drone-01 (CLOSED 7e7e84d): _CaptureOneRedirect no-follow pattern; captures Location header from drone's first 303 instead of following gitea's chain to /user/login
  • DG4.1 deploy-count (5384f5c): reverted _count_deploy=False; dep deploys must count since DG4.1 formula is expected = 1 + deps_count

Blocked items

(none)


Verification recipe (for Adversary M1 check)

To be written when M1 is claimed.