Expand description
The public boundary’s budget workload, over real Git and the production registry. The public boundary’s budget workload: one host the release-binary journeys time the publication term check and an export over.
Twenty registered private repositories, each committing a manifest and a term
declaration that derive exactly TERMS_PER_IDENTITY terms, and one registered
public repository with a branch adding PATHS files of neutral UTF-8 text,
BYTES in all. One of the private repositories carries the same files on a
branch, confined to one directory, for an export. Everything is built with real
git — fast-import for the large commits — and the registry is written through
onevcs’s own test-support bridge. Nothing here matches, diffs, derives or exports:
the journeys drive the release binary for all of that.
Every owner, name and term is synthetic.
Structs§
- Workload
- A generated host.
Constants§
- BYTES
- Bytes of UTF-8 text across those paths.
- DESTINATION
- The public repository every write lands in.
- EXPORT_
BRANCH - The branch of the export’s source that carries the directory to export.
- EXPORT_
DIRECTORY - The directory the export copies.
- IDENTITIES
- Registered private repositories in the check’s scope.
- PATHS
- Paths the publication adds, and the export copies.
- PUBLICATION_
BRANCH - The branch of the public repository that carries the published work.
- TERMS_
PER_ IDENTITY - Terms each of them derives: its
owner/name, its owner, its name, its package, and 96 declared terms.