wanjakrah/agiledancers
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

S6: record production deployment and recovery evidence #13

Merged
wanjakrah merged 3 commits from docs/S6-production-validation into main 2026-11-03 16:13:53 +01:00
Conversation 0 Commits 3 Files Changed 5 +2329 -41
wanjakrah commented 2026-11-03 15:35:36 +01:00
Owner
Copy Link

Records the successful main build and first real Gitea deployment of v1.0.0 at http://192.168.2.28:8088, including annotated tag identity, deployed digests, native duplicate-release rejection, branch exclusion and downloaded diagnostic artifacts. Adds the actual DSM firewall rules required for frontend/backend communication and moves S6 to IN_REVIEW.

Twelve isolated real NAS checks passed for failure recovery, exact-SHA retry, distinct-version rollback, missing/unverified/stale releases, lock contention, first-release failure and manual recovery after failed recovery or an ambiguous state commit. Their virtual-tag adapter boundary is stated explicitly; production remained on v1.0.0 throughout and test containers/network were removed. Persistent-data acceptance remains conditional on S16.

Validation: successful main build #37, production deployment #38, expected duplicate rejection #39 and branch skip #40. Real artifacts were downloaded and inspected; final production state and test cleanup were independently checked. Documentation only; git diff --check passed and [skip ci] avoids rebuilding unchanged application code.

Records the successful main build and first real Gitea deployment of v1.0.0 at http://192.168.2.28:8088, including annotated tag identity, deployed digests, native duplicate-release rejection, branch exclusion and downloaded diagnostic artifacts. Adds the actual DSM firewall rules required for frontend/backend communication and moves S6 to IN_REVIEW. Twelve isolated real NAS checks passed for failure recovery, exact-SHA retry, distinct-version rollback, missing/unverified/stale releases, lock contention, first-release failure and manual recovery after failed recovery or an ambiguous state commit. Their virtual-tag adapter boundary is stated explicitly; production remained on v1.0.0 throughout and test containers/network were removed. Persistent-data acceptance remains conditional on S16. Validation: successful main build #37, production deployment #38, expected duplicate rejection #39 and branch skip #40. Real artifacts were downloaded and inspected; final production state and test cleanup were independently checked. Documentation only; git diff --check passed and [skip ci] avoids rebuilding unchanged application code.
wanjakrah added 1 commit 2026-11-03 15:35:36 +01:00
Record S6 production and NAS recovery acceptance [skip ci] 3369b9a81c
wanjakrah added 1 commit 2026-11-03 16:12:34 +01:00
testfile
Some checks failed
Build, test and publish / verify (push) Has been cancelled
Details
95aa8c6302
wanjakrah added 1 commit 2026-11-03 16:13:45 +01:00
updated spec status
All checks were successful
Build, test and publish / verify (push) Successful in 6m5s
Details
95430691e4
wanjakrah merged commit b92fac1d1a into main 2026-11-03 16:13:53 +01:00
wanjakrah deleted branch docs/S6-production-validation 2026-11-03 16:13:53 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gituser renovate-bot wanjakrah
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wanjakrah/agiledancers#13
Delete Branch "docs/S6-production-validation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?