This commit is contained in:
@@ -3,7 +3,9 @@
|
||||
De workflow staat in `.gitea/workflows/build.yaml`. Elke branchpush bouwt en test
|
||||
backend en frontend, bouwt twee images en draait Playwright tegen die containers.
|
||||
Alleen `main` mag daarna images publiceren. Er vindt geen deployment plaats.
|
||||
Tagpushes en aparte pull-requestevents starten geen extra workflow.
|
||||
Tagpushes en aparte pull-requestevents starten geen extra workflow. Een auteur
|
||||
kan een branchbuild bewust overslaan met een door Gitea ondersteunde markering,
|
||||
zoals `[skip ci]`; dit is expliciet toegestaan.
|
||||
|
||||
## Java-bronbestanden uitvoeren
|
||||
|
||||
@@ -92,9 +94,9 @@ Runner en containers moeten de Synology en internetdownloads kunnen bereiken.
|
||||
Repository: `wanjakrah/agiledancers`, hoofdbranch: `main`.
|
||||
Actions staat voor deze repository al aan. Controleer zo nodig op de Synology
|
||||
`app.ini` onder `[actions]` de instelling `ENABLED = true` en de Actions-feature
|
||||
onder repositoryinstellingen. Stel `SKIP_WORKFLOW_STRINGS` leeg in als ook commits met teksten als `[skip ci]`
|
||||
verplicht moeten draaien, zoals de afspraak elke branchpush vereist.
|
||||
Wijzig serverconfiguratie alleen indien nodig.
|
||||
onder repositoryinstellingen. De standaard `SKIP_WORKFLOW_STRINGS`, waaronder `[skip ci]`, mogen blijven staan:
|
||||
bewust overslaan is door de maintainer toegestaan. Iedere gewone branchpush start
|
||||
een pipeline. Er hoeft daarvoor geen serverinstelling te worden gewijzigd.
|
||||
|
||||
Stel bij repository **Settings → Actions** in:
|
||||
|
||||
@@ -129,7 +131,8 @@ runnerregistratietoken naar
|
||||
tokenwaarden. Voor handmatige inrichting kun je dat registratietoken uit de
|
||||
repository-instellingen halen en in hetzelfde bestand plaatsen.
|
||||
|
||||
Controleer de artifactretentie op de server: een workflow vraagt veertien dagen
|
||||
De bevestigde Gitea 1.25.4-configuratie heeft geen `[actions]`-sectie: de defaults
|
||||
zijn negentig dagen voor artifacts en 365 dagen voor logs. Een workflow vraagt veertien dagen
|
||||
via `retention-days: 14`. Een kortere serverlimiet of het vroegtijdig verwijderen
|
||||
van workflowruns mag die periode niet inkorten. Artifactretentie geldt voor
|
||||
testdiagnostiek; gepubliceerde containerimages worden niet automatisch verwijderd.
|
||||
|
||||
@@ -1,8 +1,10 @@
|
||||
# S4 verification evidence
|
||||
|
||||
Date: 2026-10-28. Status: repository implementation and local container verification
|
||||
passed; Gitea and runner configuration are operational. Main publication is
|
||||
awaiting approval to merge PR #1. S4 is **not complete**.
|
||||
Updated: 2026-10-29. S4 is **complete**. Main publication/pullback passed in run
|
||||
#7. Real registry recovery, rerun and stale-main checks passed against isolated
|
||||
validation image repositories. Server defaults are confirmed from the maintainer's
|
||||
configuration report and Gitea 1.25.4 documentation; explicit skip markers are an
|
||||
accepted exception to branchpush triggering.
|
||||
|
||||
## Verified locally
|
||||
|
||||
@@ -51,18 +53,21 @@ Local image IDs (not registry digests):
|
||||
- Backend: `sha256:bd77a46e3dbdcaea9662d21c608098999fe17dfdf241cd28a24a935f47401f61`.
|
||||
- Frontend: `sha256:ce8e6ab21fb8f9cbee280ac2c4d7b4ca24a30e899a457382f1e45c6baf99dfb6`.
|
||||
|
||||
## Remaining operational acceptance
|
||||
## Operational acceptance
|
||||
|
||||
- [x] Synology architecture confirmed by the maintainer: `x86_64`,
|
||||
`linux/amd64`; repository variable `TARGET_PLATFORM=linux/amd64` configured.
|
||||
- [x] Activate and verify the Docker Desktop HTTP-registry setting.
|
||||
- [x] Repository `REGISTRY_USER`/`REGISTRY_TOKEN` secrets configured using the
|
||||
supplied token files. A temporary Docker login with the registry token
|
||||
succeeded; actual publication still awaits a main-branch merge.
|
||||
succeeded; actual main publication and pullback are now confirmed below.
|
||||
- [x] Runner ID 1 (`agiledancers-mini-pc`) registered, service started and
|
||||
online in Gitea. Real feature/failure jobs ran on this runner.
|
||||
- [ ] Confirm server settings permit every branchpush (including messages with
|
||||
skip strings) and retain uploaded diagnostic artifacts for fourteen days.
|
||||
- [x] The maintainer reports no `[actions]` section in app.ini. Gitea 1.25.4
|
||||
therefore uses the documented artifact/log defaults of 90/365 days; the
|
||||
workflow explicitly requests fourteen days for diagnostic artifacts.
|
||||
The maintainer accepts intentional `[skip ci]`-style opt-outs. No server
|
||||
change or SSH access was required.
|
||||
- [x] [Feature run #1](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/1),
|
||||
API run ID 2, commit `74a5aa12377d4a62cdebe1dcd6e8a8e1443b33fb`: succeeded,
|
||||
two container E2E tests passed, publication skipped. Diagnostic ZIP was
|
||||
@@ -73,14 +78,16 @@ Local image IDs (not registry digests):
|
||||
backend test; imagebuild/publication did not run. Diagnostic ZIP was
|
||||
downloaded and verified (15 files). The probe is absent from the real
|
||||
featurebranch.
|
||||
- [ ] Real main run: record URL/run ID, both full-SHA images, successful pullback,
|
||||
registry digests and the two `main` aliases.
|
||||
- [ ] Real rerun/partial-publication recovery and stale-main evidence: record
|
||||
run IDs and unchanged existing commit digests.
|
||||
- [x] Main run #7 (API run/job ID 8) published both full-SHA images, pulled
|
||||
them back and updated/pulled both `main` aliases; digests are recorded below.
|
||||
- [x] Real publication-code probes against the Synology registry passed:
|
||||
partial recovery preserves the first image, reruns preserve both commit
|
||||
digests, and an older commit cannot move current main aliases. Details and
|
||||
evidence are recorded below.
|
||||
|
||||
The isolated publication tests provide automated control-flow coverage; they do
|
||||
not substitute for real authenticated registry/Gitea acceptance runs. No application
|
||||
images have been published and no application has been deployed by this work.
|
||||
not substitute for real authenticated registry/Gitea acceptance runs. Application
|
||||
images have now been published by main; no application deployment is performed.
|
||||
|
||||
|
||||
Gitea 1.25 does not populate `gitea.run_attempt`; the workflow generates a unique
|
||||
@@ -90,21 +97,21 @@ were verified by downloading the run-page archive URLs. This is separate from
|
||||
artifact availability and does not require a server upgrade.
|
||||
|
||||
|
||||
## Ready for review; main merge not authorized
|
||||
## Historical review state before the main merge
|
||||
|
||||
[PR #1](http://192.168.2.28:3000/wanjakrah/agiledancers/pulls/1) remains open at
|
||||
the maintainer's explicit request. No main merge or application image publication
|
||||
was performed.
|
||||
[PR #1](http://192.168.2.28:3000/wanjakrah/agiledancers/pulls/1) was initially left open at
|
||||
the maintainer's explicit request. Main merge and publication were postponed at
|
||||
that stage; the maintainer has since merged it.
|
||||
|
||||
[Feature run #3](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/3),
|
||||
API run/job ID 4, commit `834584dae06b5976936a5e739871f1164cf81bcd`, succeeded.
|
||||
The two container E2E tests passed and diagnostics were uploaded as
|
||||
`diagnostics-4-20261028164607460012324`, confirming unique attempt names work.
|
||||
|
||||
The main branch currently contains only its initial commit. PR #1 therefore
|
||||
Before this merge, main contained only its initial commit. PR #1 therefore
|
||||
includes the prior application history from `feature/setup` as well as S4. Its
|
||||
scope is documented in the PR description. A main merge needs explicit approval;
|
||||
only then can real main publication/pullback/rerun acceptance be completed.
|
||||
scope is documented in the PR description. The maintainer subsequently merged that full history. Publication and pullback
|
||||
are confirmed below; the remaining acceptance evidence is still tracked above.
|
||||
|
||||
|
||||
## Java 25 helper migration
|
||||
@@ -113,5 +120,92 @@ CI orchestration, setup and behavior tests now run through `java ci/Ci.java`.
|
||||
The shell/Python helpers have been removed. The source launcher compiles helper
|
||||
classes in memory without external dependencies or preview flags. Fifteen Java
|
||||
behavior tests pass, including JSON/configuration preservation, publication gates,
|
||||
partial recovery and process deadlines. A real feature run validates this revision
|
||||
before updating the existing open PR; no merge to main is authorized.
|
||||
partial recovery and process deadlines. Feature run #6 passed for the Java implementation before the maintainer merged
|
||||
PR #1 into main.
|
||||
|
||||
|
||||
## Main publication confirmed after merge
|
||||
|
||||
[Main run #7](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/7), API
|
||||
run/job ID 8, completed successfully for commit
|
||||
`2356a31aa612c8b0ce4b386a0a65da6589e23285`.
|
||||
|
||||
Downloaded and inspected artifact `diagnostics-8-20261029144539933186842`.
|
||||
Its verified-commit marker, publication log and digest files confirm publication
|
||||
and pullback of both commit tags and both moving main aliases:
|
||||
|
||||
| Image | Digest for the full-SHA tag and main alias |
|
||||
| --- | --- |
|
||||
| `192.168.2.28:3000/wanjakrah/agiledancers-backend` | `sha256:483f4593716f94d1c6a7851519b80399b40600e9e49db5b656abed14b4552e93` |
|
||||
| `192.168.2.28:3000/wanjakrah/agiledancers-frontend` | `sha256:f9be998187751e13a81cbed809938837a3b80fdbfdd122c2126c9792c4320077` |
|
||||
|
||||
This closed the original merge/publication blocker. The remaining acceptance
|
||||
checks have since been completed as recorded below.
|
||||
|
||||
|
||||
## Final acceptance: recovery, rerun and stale-main protection
|
||||
|
||||
Completed on 2026-10-29. These were real command-line publication probes using the
|
||||
production `Pipeline`/`Commands` implementation against the Synology registry,
|
||||
not a second full Gitea workflow run. The test adapter redirects Docker write
|
||||
references to dedicated validation repositories and refuses application-image
|
||||
pushes. Main-head checks use the actual Gitea API.
|
||||
|
||||
The verified images from main run #7 were used as the current source. The older
|
||||
images came from the previously successful feature run #6. The main commit is
|
||||
`2356a31aa612c8b0ce4b386a0a65da6589e23285`; the older commit is
|
||||
`aea792307c5d3be43e17c11db3b9f5845dbd5f14`.
|
||||
|
||||
Test repositories:
|
||||
|
||||
- `192.168.2.28:3000/wanjakrah/s4-validation-1793286292474-backend`
|
||||
- `192.168.2.28:3000/wanjakrah/s4-validation-1793286292474-frontend`
|
||||
|
||||
Evidence/results:
|
||||
|
||||
1. Publication was deliberately stopped after backend publication and before
|
||||
frontend publication. The operation failed; the backend tag existed and the
|
||||
frontend tag did not.
|
||||
2. Recovery published the missing frontend image and retained the backend digest.
|
||||
3. A repeat publication retained both full-SHA digests and pushed only the two
|
||||
moving validation aliases. No immutable commit tag was pushed again.
|
||||
4. The older source images were published to the same isolated repositories.
|
||||
The real Gitea main-head check detected the newer commit. No moving-alias write
|
||||
was attempted, and before/after manifest hashes remained identical.
|
||||
5. Application `main` manifests were compared before and after the probes and
|
||||
remained unchanged.
|
||||
|
||||
The backend and frontend immutable digests match the run #7 digests recorded
|
||||
above. Manifest comparison hashes for the validation main aliases:
|
||||
|
||||
| Alias | Before and after SHA-256 of inspected manifest |
|
||||
| --- | --- |
|
||||
| Backend main | `b4438f0d32eae92632e1f3c106ca9c4538c87d61d6feda9e0184dd8749b46d8c` |
|
||||
| Frontend main | `3d2bebc8da4297c54eebeb43ce0f00e61a61e9216dde27c81f08be69cd6c7335` |
|
||||
|
||||
Raw local evidence is retained under `ci/artifacts/s4-final-acceptance/`, including
|
||||
`results.json`, `partial-publication.log`, `recovery.log`, `rerun.log`,
|
||||
`confirmed-rerun.log` and `stale-main.log`. The isolated validation images remain
|
||||
available as acceptance artifacts; they are not deployed application instances.
|
||||
|
||||
A temporary registry-login timeout interrupted the first stale-run probe. It
|
||||
failed visibly and cleaned up temporary login state. Retrying the remaining
|
||||
checks succeeded; the already-passed recovery/rerun evidence was retained.
|
||||
|
||||
## Server configuration closure
|
||||
|
||||
The maintainer inspected the Synology-hosted Gitea configuration and confirmed
|
||||
that `[actions]` is absent. Gitea 1.25.4 defaults are:
|
||||
|
||||
- Artifact retention: 90 days by default; the workflow's artifact upload requests
|
||||
fourteen days explicitly.
|
||||
- Job log retention: 365 days by default.
|
||||
- Intentional skip strings such as `[skip ci]` are recognized by default.
|
||||
|
||||
The maintainer explicitly approved documenting these skip strings as exceptions:
|
||||
ordinary branchpushes trigger CI, while an author can intentionally opt out with
|
||||
an existing supported marker. No Gitea configuration change or broad NAS access
|
||||
is necessary. This is the agreed interpretation of the trigger criterion.
|
||||
|
||||
Sources: [Gitea 1.25 Actions settings](https://docs.gitea.com/1.25/administration/config-cheat-sheet/#actions-actions),
|
||||
[installed-version defaults](https://github.com/go-gitea/gitea/blob/v1.25.4/modules/setting/actions.go).
|
||||
|
||||
Reference in New Issue
Block a user