1. 17 Dec, 2021 1 commit
    • Ben Avison's avatar
      Enable all jobs in detached pipelines · dc064d26
      Ben Avison authored
      When working on an unrelated issue, it became clear that the reason why
      previously only the `merge_log` and `merge_whitesp` jobs appeared in
      detached pipelines (the ones that relate to an open MR) was really because
      they include a `rules` section. It is as though in the absence of a `rules`
      section, a default one applies, which adds the job to the pipeline only if
      that pipeline was due to an update of a branch or tag ref. When `rules` was
      present for a job, it overrides the default, and is evaluated irrespective
      of the the pipeline trigger.
      Now, it's useful to have all the jobs present in detached pipelines. The
      latest detached pipeline state, and its associated artifactes, are displayed
      at the top of the "Overview" tab of each MR page, and a new one can be
      easily triggered from the "Run pipeline" button at the top of the MR page's
      "Pipelines" tab, without having to navigate to the contributor's fork project
      (which may not even be public). It's also a problem that the `cleanup` job
      wasn't being run for detached pipelines, since over time that risks filling
      up the disc space on the runner machine.
      It turns out all of this can be implemented simply by adding a `workflow`
      section which defines a new default set of rules, which adds jobs to
      detached pipelines as well as ones for branches and tags.
  2. 01 Sep, 2021 1 commit
  3. 08 Jun, 2021 1 commit
  4. 03 Jun, 2021 2 commits
  5. 01 Jun, 2021 2 commits
    • Ben Avison's avatar
      Fix rom_IOMD32 jobs · 14297559
      Ben Avison authored
      These jobs were trying to fetch a build tree from a non-existent superproject
      `Products/IOMD32` when they should have referenced `Products/IOMDHAL`.
    • Ben Avison's avatar
      Reduce disc space requirements for GitLab Runner server · 51bd4664
      Ben Avison authored
      On the Runner machine, each fork of each project gets its own directory,
      which is left in the state which the latest job for whatever pipeline was
      most recently run on it. This typically will include a large number of
      object and binary files, which are of no use to anyone (anything of interest
      will already have been packaged up into an artifact and uploaded to the
      main GitLab server). Address this by adding an additional job to the end of
      each pipeline, which does a `git clean` (it's worth leaving these in place
      to reduce the bandwidth requirement when doing a `git fetch` when a pipeline
      is next run for the fork).
      The Runner machine also stores cache files for each fork of each project, at
      least for jobs that complete fully successfully (and there are an increasing
      number of these). The way our pipelines use caches, these are tarballs of
      pre-built source trees for each target platform. These take up less space
      than the temporary files noted above, but will now become the dominant user
      of disc space. To address this, abandon use of GitLab Runner's own cache
      facility, and take advantage of the fact that shell executors actually have
      visibility of the gitlab-runner user's whole home directory to maintain a
      single, cached version of each tarball, shared across all forks of all
      projects. This is stored within ~/cache, but namespaced under ~/cache/common
      to avoid collisions with any users of GitLab Runner's cache facility.
  6. 17 May, 2021 1 commit
  7. 14 May, 2021 1 commit
    • Ben Avison's avatar
      Work around bug in git 2.27.1 · db1f5999
      Ben Avison authored
      For these versions, "git submodule update --remote" will fail for any
      submodules that don't specify a branch in .gitmodules, and which are
      currently checked out on a remote tracking branch that tracks a remote
      other than "origin". For our pipelines, this means almost any submodule
      which has a CrossCompilationSupport branch which has not yet been merged.
      Work around it by first doing "git submodule update" without "--remote",
      which will put all submodules into detacehd HEAD state.
  8. 23 Dec, 2020 1 commit
  9. 11 Dec, 2020 2 commits
    • Ben Avison's avatar
      Fix pipeline failures for established forks · 6a7e6b2b
      Ben Avison authored
      If the following happens:
      * a GitLab runner recursively clones a superproject
      * one or more submodules has changes upstream and the submodule references in
        the superproject have been updated to point to it
      * a new pipeline is launched for the new superproject revision
      then, while the runner would fetch changes to the superproject, it wasn't
      doing so for the submodules. Ironically, we do both `git submodule update`
      and `git submodule update --remote` in different pipeline stages and the
      latter includes an implicit submodule fetch - but that was the later stage
      which we don't get as far as.
      To fix this, while retaining the pipeline stage order, include an explicit
      fetch in the earlier stage (and remove the implicit fetch in the later one,
      since that now merely wastes time).
    • Ben Avison's avatar
      Fix generation of IOMDHAL.yml · 9c61e2f0
      Ben Avison authored
      This one is a special case where the superproject name mismatches the
      corresponding Env (and thus Components) file.
      Our own CI script also didn't previously support the *removal* of an
      autogenerated YAML file. This should be a rare occurrence, but it's best
      to automate this also. Also support force-pushing to the submodule; this
      will be required in most cases where the pipeline was triggered by a
      force-push to *this* project.
  10. 25 Nov, 2020 1 commit