1. 07 Jan, 2021 2 commits
  2. 22 Dec, 2020 2 commits
  3. 13 Nov, 2020 1 commit
  4. 08 Oct, 2020 2 commits
  5. 05 Oct, 2020 1 commit
  6. 01 Oct, 2020 2 commits
  7. 30 Sep, 2020 2 commits
  8. 29 Sep, 2020 3 commits
  9. 23 Sep, 2020 1 commit
  10. 16 Sep, 2020 3 commits
  11. 12 Jun, 2020 8 commits
  12. 11 Jun, 2020 1 commit
  13. 10 Jun, 2020 2 commits
  14. 03 Jun, 2020 4 commits
  15. 02 Jun, 2020 2 commits
  16. 29 May, 2020 3 commits
    • Brad King's avatar
      gitlab-ci: pin macOS and Windows jobs to nonconcurrent runners · 0eebd0a0
      Brad King authored
      On macOS and Windows, our jobs use a `GIT_CLONE_PATH` that does not
      contain `$CI_CONCURRENCY_ID` so that the build and test jobs always use
      the same path.  Since we use shell runners for these platforms, all
      concurrent jobs would use the same path and conflict.  Therefore we can
      only use runners with a concurrency level of 1 for jobs in the `build`
      and `test` stages.  However, jobs in the `test-ext` stage configure a
      new build tree for the tests and therefore can use `$CI_CONCURRENCY_ID`
      and support shell runners with higher concurrency levels.
      
      Prepare to make that distinction in the future by pinning all jobs to
      runners with a `nonconcurrent` tag.
      0eebd0a0
    • Brad King's avatar
      gitlab-ci: update macOS jobs to Xcode 11.5 · 0508a80c
      Brad King authored
      0508a80c
    • Brad King's avatar
      gitlab-ci: pin windows and macos jobs to runners with matching toolsets · 0d5a1fd6
      Brad King authored
      The toolsets available on machines hosting shell runners will evolve
      over time.  Require the runners to have tags indicating that they have
      specific toolsets available.  When toolsets are eventually removed from
      a runner, its tags can then be updated accordingly to prevent pipelines
      created for old commits from ever running on them.
      0d5a1fd6
  17. 28 May, 2020 1 commit