mesh-catalog

Files

T

jochen 3d42988afa Hold every build module to ending what a previous process left running (issue 1890)

A replaced mesh-build-go left a check ask's step running and its start
sweep spared it (issue 1890, note 21). mesh-build-go, mesh-build-node and
mesh-build-image pin mesh-sdk 981a35b5, whose steps name their owner and
whose sweep ends another owner's at once; each runs the sweep through one
method that main calls and that its test runs through the conformance
kit's left-running case. The failurekit check now refuses a build module
whose tests do not run that case, test step or not.

2026-10-27 01:22:13 +01:00

build-candidate.json

Hold every build module to ending what a previous process left running (issue 1890)

2026-10-27 01:22:13 +01:00

build-trunk.json

Hold every build module to ending what a previous process left running (issue 1890)

2026-10-27 01:22:13 +01:00

fetch.json

Hold every build module to ending what a previous process left running (issue 1890)

2026-10-27 01:22:13 +01:00

README

Fail a push whose digest file cannot be read; test the image steps through a real bus against captured shapes (issue 1703)

2026-10-22 10:34:37 +02:00

README

The stored steps (what a step ends on in the module's `steps` state) of a fetch (fetch.json), a candidate's build
(build-candidate.json, no publish) and a trunk build (build-trunk.json, publish), as buildstep writes them, with ids, times,
the workspace, the commit, digests and the registry's address put to fixed words (STEPID, WORKSPACE, COMMIT, REGISTRY, one
sha256 digest). Written by capture_test.go (MESH_UPDATE_CAPTURED=1) from the unit tests' fake runner on 2026-10-22, and
compared by bus_integration_test.go with the steps a real bus holds. mesh-delivery-builder's tests copy these files.