Design 47 H2: H-A-403, the install ask's form and the install archive's version
This commit is contained in:
@@ -271,3 +271,13 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
an unmerged one is left out); the answer holds at most 768 KB with `capped`, `total` (the numbers in the range) and
|
||||
`cursor` (the next number, given back as `from`), each row {number, merge-commit, merged-at, call (the merge call id
|
||||
when a kept call merged it, else none)}. §811's cap holds for every read tool, this one included. P3.
|
||||
- **H-A-403 (the install ask's form and the install archive's version, 00:56)** BM3, §800. (1) Every ask on a build
|
||||
seat's queue has one form: the install is a buildstep.StepAsk of kind `install` (language node, the module, commit and
|
||||
fingerprint, and an `install` job holding InstallAsk's fields); the node-build-node accept's body is that StepAsk, and
|
||||
RunAsk dispatches the kind. Where the seat's queues are per step kind, `install` is its own queue on node-build-node
|
||||
alone (the Go and image build seats never install). (2) The install archive is the module's artifact
|
||||
`<module>:node-modules` (kind archive), which the Node build module derives for a module whose check-needs names
|
||||
node-build-node and which the builder's reservation covers like every artifact of the module's build, under the
|
||||
build's version; the install ask carries that version (the runner reads it from the seat mesh-builds' reserved, as it
|
||||
reads the publish's), and the install publishes the archive under it, so H-A-387's reservation check holds. P3,
|
||||
H-A-373, H-A-399.
|
||||
|
||||
Reference in New Issue
Block a user