1. 17 Dec, 2020 2 commits
  2. 16 Dec, 2020 1 commit
  3. 20 Nov, 2020 2 commits
  4. 19 Nov, 2020 1 commit
    • Peter Hutterer's avatar
      Split out the various jobs into child pipelines · 30074862
      Peter Hutterer authored
      This helps a lot with the layout of the pipelines: since bootstrapping and
      each distribution pipeline are now stand-alone pipelines, we don't need to
      worry about includes or naming every single stage we may need etc.
      Our main pipeline just gets down to bootstrapping, then each distro
      pipeline, all of which run parallel.
      The distro pipelines have to wait for bootstrapping to be complete so our
      pipeline is less efficient than before where non-qemu jobs could start as
      soon as their bootstrapping image completed. But the pipelines are less
      complicated to maintain and generated, so let's take that hit.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  5. 05 Nov, 2020 3 commits
    • Jonas Ådahl's avatar
      Sprinkle architecture awareness · 9673e0a1
      Jonas Ådahl authored
      This means jobs or abstract jobs that are specific to a single
      archtecture now all are postfixed with that architecture. That means
      e.g. .bootstrap became .bootstrap@x86_64, while .bootstrap@aarch64
      remained the same.
      For the jobs it the CI pipeline, fedora:ci@container-build became
      fedora:ci@container-build@x86_64, alpine:latest@container-build became
      alpine:latest@container-build@x86_64, debian@cache-container-build
      became debian@cache-container-build@x86_64, and so on.
      The distribution images does not have the archtecture in the name due to
      a limitation in the number of subdirectories allowed in the gitlab
      registry. Instead the achitecture is added to the relevant tag. That
      means that fdo-ci-221155 became fdo-ci-x86_64-221155, while the image
      remained at e.g ../ci-templates/alpine/latest.
      This confusingly means that aarch64 builds, previously seemingly
      extending "generic" abstract jobs, now extend x86_64 ones, and while
      this looks confusing is how it worked in practice already.
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
    • Jonas Ådahl's avatar
      Bump fedora version to 33 · bbb9b3aa
      Jonas Ådahl authored
      This makes it necessary to pass -oPubkeyAcceptedKeyTypes=ssh-rsa to ssh
      due to https://bugzilla.redhat.com/show_bug.cgi?id=1881301
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
    • Jonas Ådahl's avatar
      Imitate buildah description used on quay.io · 64c55226
      Jonas Ådahl authored
      This makes it possible to run ci-templates on more locked down CI
      runners, e.g. those over at gitlab.gnome.org.
      for details.
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
  6. 21 Jul, 2020 1 commit
    • Benjamin Tissoires's avatar
      Bump bootstrap base image and packages · 0a522a46
      Benjamin Tissoires authored
      A few changes that are worth mentioning:
      - we no longer lock the buildah/podman versions as the bugs
        that prevented us to run those in a privileged docker
        containers are now fixed upstream and in fedora
      - we need to install runc in addition to crun in the base
        buildah image to accomodate cgroups v1 and v2
      - the qemu image now inherits from the base buildah image
        allowing us to not have to redeclare the base packages
        we need there, and to not have to run the entire
        `bootstrap.sh` script there to have a working container
      Signed-off-by: Benjamin Tissoires's avatarBenjamin Tissoires <benjamin.tissoires@gmail.com>
  7. 25 Apr, 2020 1 commit
  8. 24 Apr, 2020 2 commits
  9. 21 Apr, 2020 1 commit
    • Peter Hutterer's avatar
      ci: add the ci for the FDO_BASE_IMAGE · 8becba49
      Peter Hutterer authored
      As suggested by Benjamin, this merely runs a container-build job off
      the base image without any "content". The order (for Arch) is thus:
      arch:latest@container-build creates an image with curl+wget installed
      and pushes that to the registry.
      arch:latest@base-image starts with that base image but doesn't install
      anything. The DISTRO_EXEC script runs curl and wget though - which we
      expect to be present since we have our custom base image. If that
      succeeds we don't need to do anything else, we expect the rest to work
      since it's just the container-build job.
      The only unfortunate hack is that we cannot use the global
      FDO_DISTRIBUTION_TAG to reference the image. Gitlab doesn't do
      double-expansion of variables so we need to hardcode the same value.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  10. 16 Mar, 2020 8 commits
  11. 10 Mar, 2020 1 commit
  12. 06 Mar, 2020 1 commit
    • Benjamin Tissoires's avatar
      templates: mount the /cache folder RW · a1699326
      Benjamin Tissoires authored
      `/cache` is often used to speed up compilation with `ccache`. We should
      allow the users of CI templates to mount this directory if it exists
      so they can set up their runners as they wish and benefit from `ccache`.
      Note that to allow the CI to test that we can mount the `/cache` folder.
      So we introduce a new variable `CACHE_DIR`, which defaults to `/cache`,
      that allows to tell which folder needs to be mounted as `/cache` in the
      `buildah run $DISTRIBUTION_EXEC` stage.
      - this allows to overwrite the `/cache` folder if it already exists in
        the current runner
      - this also allows to export its content as an artifact in the CI job
      Fixes #5
      Signed-off-by: Benjamin Tissoires's avatarBenjamin Tissoires <benjamin.tissoires@gmail.com>
  13. 05 Mar, 2020 6 commits
  14. 26 Feb, 2020 1 commit
  15. 17 Feb, 2020 1 commit
  16. 11 Dec, 2019 1 commit
  17. 05 Dec, 2019 3 commits
  18. 03 Dec, 2019 1 commit
  19. 29 Nov, 2019 3 commits