summaryrefslogtreecommitdiffstats
path: root/.gitlab
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | ci: Enable Swift tests in debian10-ninja job in non-MR pipelinesBrad King2022-02-252-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | The Swift compiler is too big to put in the Debian base image, so download it in this specific job instead.
* | | | | ci: Move debian10_ninja job environment to shell scriptBrad King2022-02-252-1/+1
| | | | |
* | | | | ci: Add Swift compiler runtime dependencies to Debian base imageBrad King2022-02-252-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The actual compiler is too large to put in the base image. Install its dependencies so we can download and run it in a job. Note that Swift binaries are only available for `x86_64`.
* | | | | ci: Verify content of ironpython package in Debian base imageBrad King2022-02-251-2/+4
| | | | | | | | | | | | | | | | | | | | Also clean up more temporary files.
* | | | | ci: Explicitly enable CTest.Update{BZR,CVS,GIT,HG,P4,SVN} testsBrad King2022-02-223-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | Avoid relying on heuristics to enable these tests. Be sure they run in CI where expected.
* | | | | ci: Add bzr and p4 to Debian and Fedora base imagesBrad King2022-02-224-3/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Perforce does not provide binaries for `aarch64`, so leave it out for that architecture. Fedora now packages `breezy` instead of the original `bzr`. Note that breezy does not have the xmloutput plugin needed for `bzr log --xml`. This is also why commit 1972a75536 (Tests: Drop CTestUpdate.BZR test check for xmloutput plugin, 2022-02-04) observed that there is no `bzr xmlplugins` command.
* | | | | ci: Explicitly disable Java tests on Windows with Borland and Open WatcomBrad King2022-02-142-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | Extend the change from commit 840fa28d3d (ci: Explicitly disable Java tests on Windows, 2021-12-16) to cover Borland and Open Watcom builds.
* | | | | ci: Explicitly disable Java tests on Windows Clang buildsBrad King2022-02-101-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | Extend the change from commit 840fa28d3d (ci: Explicitly disable Java tests on Windows, 2021-12-16) to cover LLVM/Clang builds on Windows too.
* | | | | ci: Add LLVM/Clang 13.0 nightly CI jobs on WindowsBrad King2022-02-048-0/+88
| | | | | | | | | | | | | | | | | | | | | | | | | Add jobs covering the `clang-cl` front-end with Ninja and NMake. Add a job covering the `clang++` front-end with Ninja.
* | | | | Merge topic 'test-mfc-explicit'Brad King2022-02-042-0/+2
|\ \ \ \ \ | |/ / / / |/| / / / | |/ / / | | | | | | | | | | | | 9d621ceba1 Tests: Run MFC test only when explicitly enabled Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6943
| * | | Tests: Run MFC test only when explicitly enabledBrad King2022-02-032-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we used a complicated heuristic to decide whether or not to run the MFC test, but it sometimes decided incorrectly to run the test. Since that was first written, we have developed a convention for other tests to enable them via undocumented cache entries that are added only on machines known to meet the tests' requirements. Do that for MFC.
* | | | gitlab-ci: clarify name of windows fragment for building with ninjaBrad King2022-02-021-2/+2
|/ / /
* | | gitlab-ci: update to Fedora 35 base imagesBrad King2022-02-0116-35/+35
| | |
* | | gitlab-ci: update to Fedora 35 for upload jobsBrad King2022-02-011-2/+2
| | |
* | | ci: update to Fedora 35 for Linux base imagesBrad King2022-02-014-3/+3
| | |
* | | Merge topic 'ci-assertions'Brad King2022-02-012-0/+5
|\ \ \ | |/ / | | | | | | | | | | | | | | | 45feab3c00 gitlab-ci: enable assertions on fedora34-ninja jobs Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6927
| * | gitlab-ci: enable assertions on fedora34-ninja jobsBrad King2022-01-312-0/+5
| | | | | | | | | | | | | | | | | | | | | We should have at least one CI job in merge request pipelines that builds CMake with assertions enabled. We avoid using the `Debug` configuration in order to keep CI artifacts small, so instead use the `Release` configuration without `-DNDEBUG`.
| * | Merge topic 'ci-xcode-13.2' into release-3.22Brad King2022-01-251-6/+6
| |\ \ | | |/ | | | | | | | | | | | | | | | 8cb32fc8ad gitlab-ci: update macOS jobs to use Xcode 13.2 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6897
| * | ci: Explicitly disable Java tests on VS buildsBrad King2021-12-221-0/+1
| | | | | | | | | | | | | | | Extend the change from commit 840fa28d3d (ci: Explicitly disable Java tests on Windows, 2021-12-16) to cover VS builds too.
* | | Merge topic 'ci-xcode-13.2'Brad King2022-01-251-6/+6
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 8cb32fc8ad gitlab-ci: update macOS jobs to use Xcode 13.2 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6897
| * | gitlab-ci: update macOS jobs to use Xcode 13.2Brad King2022-01-251-6/+6
| | |
* | | ci: Enable ccmake on WindowsBrad King2022-01-191-0/+1
| | |
* | | ci: Explicitly disable Java tests on VS buildsBrad King2021-12-221-0/+1
| | | | | | | | | | | | | | | Extend the change from commit 840fa28d3d (ci: Explicitly disable Java tests on Windows, 2021-12-16) to cover VS builds too.
* | | Merge topic 'ci-windows-no-java'Brad King2021-12-162-1/+2
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 840fa28d3d ci: Explicitly disable Java tests on Windows Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6807
| * | ci: Explicitly disable Java tests on WindowsBrad King2021-12-162-1/+2
| | | | | | | | | | | | | | | | | | | | | Avoid searching for a Java installation on Windows hosts. This will allow some CI hosts to have Java for other projects. We already do this on macOS. While at it, clarify the macOS setting.
| * | gitlab-ci: shorten job prefixesBen Boeckel2021-11-231-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helps to maximize the amount of information visible in the GitLab web interface. Also document their meaning in the developer documentation and in the CI configuration file directly. See: https://gitlab.com/gitlab-org/gitlab/-/issues/8496
| * | Merge topic 'ci-xcode-13.1' into release-3.22Brad King2021-11-231-6/+6
| |\ \ | | |/ | | | | | | | | | | | | | | | 224d81e804 gitlab-ci: update macOS jobs to use Xcode 13.1 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6757
* | | ci: Exclude spuriously failing test from JOM nightly CI jobBrad King2021-12-091-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 3b9975d9b5 (ci: Add JOM nightly CI job, 2021-11-17) the `ExternalProject` test often fails spuriously with an internal error message from JOM. Exclude it for now pending further investigation. Prior to covering JOM in CI, it was covered by a standalone nightly build that excluded the `ExternalProject` test for the same reason.
* | | Merge topic 'ci-xcode-13.1'Brad King2021-11-231-6/+6
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 224d81e804 gitlab-ci: update macOS jobs to use Xcode 13.1 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6757
| * | gitlab-ci: update macOS jobs to use Xcode 13.1Brad King2021-11-221-6/+6
| | |
| * | Merge topic 'ci-xcode-13.0' into release-3.21Brad King2021-10-061-6/+6
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 429522e89c gitlab-ci: update macOS jobs to use Xcode 13.0 75901f0472 Tests: Fix RunCMake.XcodeProject XcodeIOSInstallCombined cases for Xcode 13.0 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6578
* | | | gitlab-ci: shorten job prefixesBen Boeckel2021-11-221-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helps to maximize the amount of information visible in the GitLab web interface. Also document their meaning in the developer documentation and in the CI configuration file directly. See: https://gitlab.com/gitlab-org/gitlab/-/issues/8496
* | | | Merge topic 'ci-gmock'Brad King2021-11-193-2/+4
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | fae34ea007 ci: add gmock to Debian base images Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6746
| * | | ci: add gmock to Debian base imagesBrad King2021-11-183-2/+4
| | | | | | | | | | | | | | | | It is already in the Fedora base images.
| * | | gitlab-ci: Update Windows jobs to VS 2022Brad King2021-11-114-15/+16
| | | |
| * | | gitlab-ci: Re-organize Windows job tagsBrad King2021-11-111-2/+2
| | | | | | | | | | | | | | | | Name the tag groups based on the VS version needed.
* | | | ci: Add JOM nightly CI jobBrad King2021-11-173-0/+44
| | | |
* | | | ci: Add NMake nightly CI jobBrad King2021-11-172-0/+18
| | | |
* | | | gitlab-ci: Factor out windows_vcvarsall_vs2022_x64 config blockBrad King2021-11-171-4/+9
| | | | | | | | | | | | | | | | Isolate the vcvarsall variables in a dedicated block.
* | | | gitlab-ci: Clarify MSVC v71 job script config block nameBrad King2021-11-171-1/+1
| | | | | | | | | | | | | | | | | | | | Rename `cmake_test_windows_{nmake => msvc}` since it fetches MSVC, not NMake.
* | | | gitlab-ci: Try upstream ninja development branch in a Windows nightly jobBrad King2021-11-152-0/+14
| | | |
* | | | gitlab-ci: Add wix, cmake, and ninja to PATH incrementally on WindowsBrad King2021-11-151-4/+5
| | | | | | | | | | | | | | | | Also run their scripts in an isolated child process.
* | | | ci: Fix vcvarsall.ps1 environment variable lookupBrad King2021-11-151-1/+1
| | | | | | | | | | | | | | | | | | | | Previously we were relying on `VCVARSPLATFORM` and `VCVARSVERSION` powershell script variables. Read them from the environment directly.
* | | | ci: Enable FindODBC and FindOpenMP tests on Windows VS buildsBrad King2021-11-122-0/+10
| | | | | | | | | | | | | | | | The packages comes with the Windows SDK and/or the compiler.
* | | | ci: Add VS 2019 nightly CI jobsBrad King2021-11-127-10/+33
| | | | | | | | | | | | | | | | | | | | Now that the primary VS jobs have been converted to VS 2022, add nightly CI jobs to cover VS 2019.
* | | | gitlab-ci: Update Windows jobs to VS 2022Brad King2021-11-114-15/+16
| | | |
* | | | gitlab-ci: Re-organize Windows job tagsBrad King2021-11-111-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | Name the tag groups based on the VS version needed, if any. Drop VS-related tags from Windows jobs that do not need any pre-installed VS version.
* | | | ci: Add MSVC v71 NMake nightly CI jobBrad King2021-11-014-0/+58
| | | |
* | | | Merge topic 'ci-scheduled'Brad King2021-10-271-2/+5
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | ada9855b78 gitlab-ci: Run manual jobs automatically only on scheduled pipelines Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !6671
| * | | gitlab-ci: Run manual jobs automatically only on scheduled pipelinesBrad King2021-10-271-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we ran manual jobs automatically in the `cmake/cmake` project integration branches. Change this to happen only when the pipeline is created by a schedule. Also, start automatic jobs in scheduled pipelines without delay.
generated by cgit v0.12 at 2025-04-11 05:07:09 (GMT)