summaryrefslogtreecommitdiffstats
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: Add macos-arm64 jobs for Ninja and XcodeBrad King2021-02-231-0/+37
| | | | For now, leave these jobs out during merge requests.
* gitlab-ci: rename macos build and test jobs to macos-x86_64Brad King2021-02-231-23/+23
| | | | | This makes room for future equivalents for other architectures. The packaging jobs produce universal binaries, so leave them as-is.
* gitlab-ci: Drop package pipeline upload jobs for release branchBrad King2021-02-101-5/+5
| | | | | The package pipeline for release versions should not upload packages automatically to our archive of nightly development versions.
* gitlab-ci: add test:debian10-aarch64-ninja jobBrad King2021-01-271-0/+13
|
* gitlab-ci: add build:centos7-aarch64 jobBrad King2021-01-271-0/+10
| | | | | Test building our release for the `aarch64` architecture. For now, leave this job out during merge requests.
* gitlab-ci: rename build:centos6-{release => x86_64}Brad King2021-01-271-7/+7
| | | | This makes room for a future equivalent for other architectures.
* gitlab-ci: consolidate release and package job infrastructureBrad King2021-01-271-9/+11
| | | | | | Use `linux_release` in names associated with building or testing release-style binaries. Add a `.linux_package` helper to adjust the release binary build behavior for package-specific jobs.
* gitlab-ci: add a job to upload macOS 10.10 binariesBrad King2021-01-071-0/+11
|
* Merge branch 'backport-rel-macos-modern' into rel-macos-modernBrad King2021-01-071-0/+12
|\
| * ci: build separate macOS packages for macOS 10.13+ and macOS 10.10+Brad King2021-01-071-0/+12
| | | | | | | | | | | | | | | | | | | | In order to support modern macOS features like Dark Mode, we need to use Qt 5.15, which requires macOS 10.13. However, we still want to support macOS 10.10 as well, for which we need to use Qt 5.9. Build separate macOS packages for these use cases. Fixes: #21606 Issue: #20825
| * gitlab-ci: add jobs to make Linux release packages for aarch64 on 3.19 branchHi Key2020-12-221-0/+23
| |
* | gitlab-ci: add jobs to make Linux release packages for aarch64Hi Key2020-12-221-0/+23
| |
* | Merge branch 'ci-fedora33-release' into ci-fedora33Ben Boeckel2020-11-131-17/+17
|\ \ | |/ | | | | | | | | | | | | | | | | | | * ci-fedora33-release: gitlab-ci: use Fedora 33 to build sources gitlab-ci: update Linux CI to use Fedora 33 ci: update to Fedora 33 for Linux builds ci: install gmock in the Fedora 31 image Tests/FindBoost/TestPython: support finding 3.8 and 3.9 clang-tidy: ignore new warnings from newer versions clang-tidy: ignore `misc-no-recursion`
| * gitlab-ci: update Linux CI to use Fedora 33Ben Boeckel2020-11-131-17/+17
| |
* | Begin post-3.19 developmentBrad King2020-10-081-3/+3
|/
* gitlab-ci: Drop package pipeline upload jobs for release branchBrad King2020-10-081-3/+3
| | | | | The package pipeline for release versions should not upload packages automatically to our archive of nightly development versions.
* gitlab-ci: add job to run test suite on Debian 10 with ninjaBrad King2020-10-051-0/+11
|
* gitlab-ci: add jobs to make Linux release packagesBen Boeckel2020-10-011-0/+23
| | | | These reuse the doc artifacts as the macOS package does.
* gitlab-ci: rename package-pipeline jobs to end in "-package"Brad King2020-10-011-8/+8
|
* gitlab-ci: add sphinx job to continuous buildBrad King2020-09-301-0/+3
|
* gitlab-ci: use separate rules for dependent jobsBrad King2020-09-301-9/+9
|
* gitlab-ci: add a job to upload source packagesBrad King2020-09-291-0/+11
|
* gitlab-ci: add a job to make source packagesBrad King2020-09-291-0/+8
|
* gitlab-ci: re-organize packaging pipelineBrad King2020-09-291-14/+16
| | | | | Move the macOS package build job into the `build` stage. Since it depends on the sphinx doc package job, add a preceding `prep` stage.
* gitlab-ci: Add GUI testing to each OSKyle Edwards2020-09-231-1/+1
|
* gitlab-ci: add a job to upload macOS binariesBen Boeckel2020-09-161-0/+15
|
* gitlab-ci: add a job to make macOS packagesBen Boeckel2020-09-161-0/+13
|
* gitlab-ci: add a job to make a doc "bundle"Ben Boeckel2020-09-161-0/+8
| | | | | This can be added to any other platform's package by reusing the artifact.
* gitlab-ci: split linux and macos shared before scriptsBen Boeckel2020-06-121-10/+9
| | | | | They're not actually the same anyways and the anchors can't be shared between the files. We can figure out refactoring in the future.
* gitlab-ci: use `extends`Ben Boeckel2020-06-121-93/+93
| | | | YAML anchors are not supported across include files.
* gitlab-ci: add a comment describing what goes into a jobBen Boeckel2020-06-121-0/+16
|
* gitlab-ci: make rules a bit more uniformBen Boeckel2020-06-121-17/+17
|
* gitlab-ci: split into multiple filesBen Boeckel2020-06-121-462/+17
| | | | | | | | Also add comments for sections to make it easier to figure out what's going on. Also rename the `cmake_test_unix_package` to be Linux-specific since it actually is.
* gitlab-ci: add an Xcode testerBen Boeckel2020-06-121-0/+33
|
* gitlab-ci: rename some scripts to be Linux-specificBen Boeckel2020-06-121-7/+6
| | | | macOS install trees have a different layout and package names.
* Merge topic 'gitlab-ci-ext-test-sets' into release-3.18Brad King2020-06-121-19/+59
|\ | | | | | | | | | | | | | | | | | | 2e7cefec03 gitlab-ci: add a cuda10.2 builder 1a2961b895 Tests: add CUDA labels to tests which are affected by CUDA 2caa7502d5 ci: support running just a set of tests with external builders 26b4cbcf93 gitlab-ci: move Makefiles Linux tests to use the package Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4877
| * gitlab-ci: add a cuda10.2 builderBen Boeckel2020-06-121-0/+31
| |
| * gitlab-ci: move Makefiles Linux tests to use the packageBen Boeckel2020-06-111-19/+28
| |
* | gitlab-ci: test QtDialog on macOSBen Boeckel2020-06-101-0/+3
| |
* | gitlab-ci: test QtDialog on WindowsBen Boeckel2020-06-101-0/+2
|/
* Merge topic 'linux-release-builders'Brad King2020-06-031-0/+54
|\ | | | | | | | | | | | | | | | | | | | | | | 922cd3affe ci: fix the project detection for CDash submissions c5b072800d gitlab-ci: add jobs for reproducing the release binaries 45f2786ff7 Release/linux: remove explicit LANG setting c540fcaa6b Sphinx/create_identifiers: handle qhp contents as utf-8 e237fc65b7 Sphinx/create_identifiers: use `not in` not `not _ in` 0aa061f6f8 Sphinx/create_identifiers: remove unused import Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4852
| * gitlab-ci: add jobs for reproducing the release binariesBen Boeckel2020-06-031-0/+54
| |
* | gitlab-ci: Update Windows builds to MSVC 19.26Brad King2020-06-031-2/+2
| |
* | gitlab-ci: support Windows jobs which support concurrent buildsBen Boeckel2020-06-031-4/+18
| |
* | gitlab-ci: support macOS jobs which support concurrent buildsBen Boeckel2020-06-031-7/+20
|/
* gitlab-ci: add a Ninja Multi-Config test jobBen Boeckel2020-06-021-0/+34
| | | | This reuses the Ninja generator's tested build.
* gitlab-ci: also build ncurses and Qt code on LinuxBen Boeckel2020-06-021-4/+4
|
* gitlab-ci: pin macOS and Windows jobs to nonconcurrent runnersBrad King2020-05-291-0/+4
| | | | | | | | | | | | | | 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.
* gitlab-ci: update macOS jobs to Xcode 11.5Brad King2020-05-291-2/+2
|
* gitlab-ci: pin windows and macos jobs to runners with matching toolsetsBrad King2020-05-291-1/+6
| | | | | | | | 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.
generated by cgit v0.12 at 2024-12-28 12:20:26 (GMT)