All checks were successful
Build and Publish TechDocs / build-and-publish (push) Successful in 1m10s
Change-Id: I4be6ec6c6ff38d93404b5ff7f28dcf6fced57099
24 lines
886 B
Markdown
24 lines
886 B
Markdown
# test-for-310--008
|
|
|
|
> **System-of-Record branch** — application code lives on `dev`.
|
|
|
|
| Branch | Purpose |
|
|
|-----------|---------|
|
|
| `dev` | Inner loop — push freely, deploys to dev env automatically |
|
|
| `staging` | Staging env — promoted from dev via PR (CI gate + 1 approval) |
|
|
| `prod` | Production — promoted from staging via PR (CI gate + 1 approval) |
|
|
| `main` | System of record — receives merges from prod after releases |
|
|
|
|
## Platform CI/CD
|
|
|
|
Workflows in `.gitea/workflows/` are **runtime-agnostic** — they read
|
|
`.platform/config.yaml` at run-time to determine build toolchain, container
|
|
port, and health endpoint. No workflow files need updating when this service
|
|
is migrated to a different runtime.
|
|
|
|
| Config key | Value |
|
|
|------------|-------|
|
|
| `runtime` | `java-springboot` |
|
|
| `health_path` | `/actuator/health` |
|
|
| `container_port` | `8080` |
|