No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-12 17:49:43 +02:00
apps feat: bootstrap Athens GitOps owner 2026-09-01 09:39:42 +02:00
docs docs: record native availability verification 2026-09-12 17:49:43 +02:00
manifests/athens chore: move both module stores to hcloud-volumes 2026-09-03 22:04:15 +02:00
tests chore: move both module stores to hcloud-volumes 2026-09-03 22:04:15 +02:00
AGENTS.md feat: bootstrap Athens GitOps owner 2026-09-01 09:39:42 +02:00
BINJOVI.md docs: record native deploy cutover 2026-09-05 21:07:25 +02:00
BINJOVI_NATIVE_DELIVERY.md docs: record native Binjovi delivery 2026-09-05 17:50:15 +02:00
README.md docs: explain native delivery and task telemetry 2026-09-09 18:07:11 +02:00

sean/athens

This repository is the GitOps owner for the two Athens Go module proxy cache tiers in the athens namespace.

  • manifests/athens/ contains the Namespace, two Deployments, two Services, and two persistent volume claims.
  • apps/athens.yaml contains the repo-native form of the singleton Argo CD Application/athens. The live application tracks this repository at main.
  • docs/OWNERSHIP.md records the source revision and the safe handoff boundary.
  • tests/ protects source parity, workload behavior, API identity, and the Application contract. Run bash tests/check.sh.

The build cache endpoint is http://athens.athens.svc.cluster.local:3000. The isolated release cache endpoint is http://athens-release.athens.svc.cluster.local:3000.

Use the fleet branch model for normal changes: feature branch to trunk, then verified release from trunk to main. Argo CD tracks main.

Binjovi owns the Build, Release, and Deploy lifecycle. The deployment target is athens-development. Its availability gate checks both cache metrics Services after Argo CD converges.

Native pipeline timing

Binjovi uses native agents for this project's Build, Release, and Deploy tasks. The configured deployment target is athens-development. The deployment checks both the Build and Release module proxy endpoints.

Select an exact successful Build when you release:

binjovictl builds athens
binjovictl release athens --build BUILD_ID --wait
binjovictl status athens

Open the project dashboard and expand an execution attempt to inspect its task timeline and available profiles. The latest completed pipeline summary includes Build and Release time as well as deployment time. Check the Deploy result separately after Release completes. Telemetry explains execution; the stored revision and verification evidence establish completion.