mirrors/flatcar-scripts
1
0
Fork 0
mirror of https://github.com/flatcar/scripts.git synced 2025-08-07 21:16:57 +02:00
Code Issues Packages Projects Releases Wiki Activity
bce3bd9031
flatcar-scripts/ci-automation
History
Kai Lueke e85a16fe1c ci-automation: allow to optionally push and sign the commit 
For test builds the commit that updates the submodules can be free-
standing but for releases we need to push it to the branch and also
sign the tag.
Add optional arguments that are used by the tag-release script in
flatcar-build-scripts.
2022-01-05 15:25:31 +01:00
..
util ci-automation: simplified CI automation unsing containers 2021-11-26 17:54:43 +01:00
ci_automation_common.sh ci-automation: allow to optionally push and sign the commit 2022-01-05 15:25:31 +01:00
ci-config.env sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00
garbage_collect.sh ci-automation/garbage_collect: remove spurious line number 2021-11-26 17:54:43 +01:00
image.sh sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00
packages.sh ci-autmation: support main- alongside alpha-, beta-... 2021-11-26 17:54:43 +01:00
README.md sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00
sdk_bootstrap.sh sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00
sdk_container.sh sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00
vms.sh sdk-container: add @krnowak's suggestions from code review 2021-11-26 17:54:43 +01:00

README.md

CI automation glue logic scripts

Scripts in this directory aim to ease automation of Flatcar builds in continuous integration systems.

Each script represents a distinct build step; each step ingests the container image of the previous step and produces a new container image for the next step. Notable exceptions are "SDK Bootstrap" (sdk.sh) which only creates an SDK tarball, and "VMs build" which does not output a container but only VM (vendor) images.

Please refer to the individual scripts for prerequisites, input parameters, and outputs.

All steps make use of a "build cache" server for pulling (https) and pushing (rsync) build inputs and artifacts.

Build steps

The build pipeline can be used to build everything from scratch, including the SDK (starting from 1. below) or to build a new OS image (starting from 3.).

SDK bootstrap build

  1. SDK Bootstrap (sdk.sh): Use a seed SDK tarball and seed SDK container image to build a new SDK tarball. The resulting SDK tarball will use packages and versions pinned in the coreos-overlay and portage-stable submodules. This step updates the versionfile, recording the SDK container version just built. It will generate and push a new version tag to the scripts repo.
  2. SDK container build (sdk_container.sh) : use SDK tarball to build an SDK container image. The resulting image will come in "amd64", "arm64", and "all" flavours, with support for respective OS target architectures. This step builds the Flatcar SDK container images published at ghcr.io/flatcar-linux.
         .---------.                 .------------.
         | scripts |                 |     CI     |
         |  repo   |                 | automation |
         `---------´                 `------------´
              |                             |
              |                   "alpha-3449.0.0-dev23"
              |                             |
              |                      _______v_______
              +------- clone -----> ( SDK bootstrap )
              |                      `-------------´
              |<- tag: sdk-3499.0.0-dev23 -´|
              |                             |
              |                      _______v_______
              +--      clone     -> ( SDK container )
              | sdk-3499.0.0-dev23   `-------------´
              |                             |
              v                             v
                      continue to OS
                       image build
                            |
                            v

OS image build

  1. Packages build (packages.sh): using the SDK container version recorded in the versionfile, build OS image packages and generate a new container image (containing both SDK and packages). This step updates the versionfile, recording the Flatcar OS image version just built. It will generate and push a new version tag to the scripts repo.
  2. Image build (image.sh): Using the container from 3., build an OS image and torcx store, and generate a new container image with everything in it.
  3. VMs build (vms.sh). Using the packages+torcx+image container from 4., build vendor images. Results are vendor-specific OS images.
       .---------.                     .------------.
       | scripts |                     |     CI     |
       |  repo   |                     | automation |
       `---------´                     `------------´
            |                                 |
            |                       "alpha-3449.0.0-dev23"
            |                                 |
            |                             ____v_____
            +---------- clone -------->  ( packages )
            |                             `--------´
            |<-- tag: alpha-3499.0.0-dev23 --´|
            |                                 |
            |                              ___v___
            +-----       clone      --->  ( image )
            |    alpha-3499.0.0-dev23      `-----´
            |                                 |
            |                               __v__
            +-----       clone      --->   ( vms )
                 alpha-3499.0.0-dev23       `---´