build(confidence-engine): add manual Jenkins deployment
This commit is contained in:
@@ -188,6 +188,20 @@ First document to read: **`docs/current-handoff.md`** (methodology continuity +
|
||||
|
||||
Implementation status last checked against source: Experiment 43 + v0.61 apparatus (tsx helper, reconstruction-only seam, focused-deconstruction schema fix). Multi-investigation architecture verified at v0.60g2+ and structurally complete. The current-state document was verified as accurate by focused code inspection of API routes, orchestrator imports/calls, and cross-module traces for all passive classifiers. No corrections were required.
|
||||
|
||||
## Deployment Automation
|
||||
|
||||
A manual Jenkins deployment pipeline has been established and is now repository-owned.
|
||||
|
||||
- **Jenkinsfile** (root) — Declarative Pipeline with three stages: `Resolve` → `Deploy` → `Verify/result`.
|
||||
- **Parameter:** `GIT_REF` (string) — user-supplied Git ref (branch, tag, or SHA). Blank value fails clearly.
|
||||
- **Resolution:** Jenkins resolves the ref to an exact commit SHA via `git ls-remote origin` before deployment. The SHA is deployed immutably.
|
||||
- **Target host:** CT 112 (`confidence-engine`, 192.168.68.73) at `/opt/confidence-engine`.
|
||||
- **Docker image:** tagged `confidence-engine:<sha>`, built on CT 112, no registry required.
|
||||
- **Environment:** production values in `/opt/confidence-engine/deploy.env` on CT 112 (not in Git). `deploy.env.example` provided as reference.
|
||||
- **Health check:** polls `http://127.0.0.1:3000/api/health`; requires `{"healthy":true}` within 60s.
|
||||
- **Rollback:** one-step rollback to the previous container image on failure (if available).
|
||||
- **Not configured in this increment:** Jenkins job, deploy.env values, SSH credential, first deployment run.
|
||||
|
||||
## 10. Post-v0.8 Methodology Learning
|
||||
|
||||
### Durable methodology principles (2026-08-19)
|
||||
|
||||
Reference in New Issue
Block a user