-
Notifications
You must be signed in to change notification settings - Fork 168
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add new multi-arch build layout mode
Add a new mode which allows cosa to manipulate multi-arch build layouts: ``` $ find builds builds builds/builds.json builds/30.1 builds/30.1/x86_64 builds/30.1/x86_64/coreos-assembler-config.tar.gz builds/30.1/x86_64/coreos-assembler-config-git.json builds/30.1/x86_64/fedora-coreos-30.1-qemu.qcow2 ... ``` A pipeline could e.g. dispatch builds for each architecture on different nodes, then group them back into a single workdir and have it manipulated by e.g. `buildupload` seamlessly. This new layout also matches the bucket layout for FCOS (see coreos/fedora-coreos-tracker#189). The basic idea is to add a `schema-version` to `builds.json` and denote the legacy behaviour as "pre-1.0.0", while `1.0.0` contains a different schema: each element in the `builds` array is now an object, which has an `id`, and a list of `archs` for which that build has been built: ``` $ cat builds/builds.json { "schema-version": "1.0.0", "builds": [ { "id": "30.1", "archs": [ "x86_64" ] } ], "timestamp": "2019-06-28T20:50:54Z" } ``` We retain backwards-compatibility by simply checking the schema version. Right now, only new workdirs will have this layout. Pipelines which use `buildprep` will fetch `builds.json` as is and key off of its contents to determine the bucket layout as well. We can write new code in the future to convert previously single-arch buckets into the new layout to then enable multi-arch.
- Loading branch information
Showing
6 changed files
with
108 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters