jochen
a641ed7d15
mesh/delivery-group group fix/121-genesis-package-registry delivering: 2 of 4 delivered
mesh/merge-gate head a641ed7d15c7 merged into trunk b12c4b82e820 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
mesh/repo-check head a641ed7d15c7 merged into trunk b12c4b82e820 — pass: its merge-check.sh passed
mesh/delivery delivered
With npm-package-registry optional, the binding file the agent's environment names may be absent, and mesh-builder failed every build on reading it. It now reads the genesis document the installer seals at genesis's packages step when no binding is present, prefers the binding when both are, and each build's log says which it resolved from (§4). A build that needs the registry - a package, an image naming .npmrc, TypeScript with an @novox/ dependency - on an agent with neither is refused before anything is built or published, naming the machine, the unbound requirement and gitea (§6); it never falls back to the public registry. The captured catalogue moves to the mesh-catalog change it is judged with.
36 lines
2.3 KiB
Plaintext
36 lines
2.3 KiB
Plaintext
What a test reads of another repository when no merge check has cloned it beside this one (internal/beside,
|
|
novox/hq issue 432). Copied from the repositories at the commits below, never written by hand. Each
|
|
module.json is kept as module.json.captured: a module.json in this repository is a module of it to the
|
|
forge and the planner, and a merge would build and register it.
|
|
|
|
The copy carries the catalogue's private details: domains, first names in module names, a node name and
|
|
private addresses. That is acceptable while mesh-controller is private; if it ever goes public, this copy is
|
|
a second place to clean besides the catalogue itself.
|
|
|
|
mesh-catalog e0bc919d4945bb5f13f971f74643a0b714cf45da modules/*/module.json, modules/nats/Dockerfile
|
|
mesh-host 7a41e120635b3f7b6cb94cca8b3fc4093e4e6110 examples/foundation-first-node.lock
|
|
mesh-sdk 33917f91ac3cc213b879b32f3c70e2aa70395f98 conformance/events/module-event.json
|
|
|
|
To move them, from this repository's root, with the two repositories checked out beside it:
|
|
|
|
rm -rf testdata/beside/mesh-catalog testdata/beside/mesh-host
|
|
mkdir -p testdata/beside/mesh-catalog testdata/beside/mesh-host
|
|
git -C ../mesh-catalog archive <commit> modules | tar -x -C testdata/beside/mesh-catalog --wildcards \
|
|
'modules/*/module.json' 'modules/nats/Dockerfile'
|
|
find testdata/beside -name module.json -exec mv {} {}.captured \;
|
|
git -C ../mesh-host archive <commit> examples/foundation-first-node.lock | tar -x -C testdata/beside/mesh-host
|
|
|
|
and write the commits here. The SDK is captured at the commit go.mod pins for git.novox.be/novox/mesh-sdk/go
|
|
(the last part of its pseudo-version; novox/hq issue 449), which internal/link's conformance test holds it to:
|
|
|
|
rm -rf testdata/beside/mesh-sdk && mkdir -p testdata/beside/mesh-sdk
|
|
git -C ../mesh-sdk archive <commit> conformance/events | tar -x -C testdata/beside/mesh-sdk
|
|
|
|
And from mesh-host at the same commit as its line above, the node-engine's placement guard, which
|
|
internal/catalogue's engine_guard_test.go holds the controller's resolved-path rules to (novox/hq issue 496),
|
|
kept as .captured so no Go tool reads it as this repository's code:
|
|
|
|
mkdir -p testdata/beside/mesh-host/internal/apply
|
|
git -C ../mesh-host show <commit>:internal/apply/placement_guard.go \
|
|
> testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
|