The build pipeline, is a sub-pipeline used to generate the build tree to use rather than the current root directory. This can be nested arbitrarily deep, but ultimately we will fall back to the current logic when no build property is found. Just like the tree after the last stage of a regular pipeline ends up in the object store, so does currently each build tree (as the build sub-pipeline really is just a regular pipeline in its own right). We may want to avoid both these instances of the implicit storing semantics, and rather make it something the caller opts-in to. However, for now that is left as a future optimization. Signed-off-by: Tom Gundersen <teg@jklm.no> |
||
|---|---|---|
| .. | ||
| base-from-yum.json | ||
| base-qcow2.json | ||
| base-with-grub2.json | ||
| base-with-locale.json | ||
| base-with-selinux.json | ||
| base.json | ||
| build-from-yum.json | ||
| noop.json | ||