gitlab-ci: harmonize with other Kitware project setups
The CI setup in VTK-m is slightly different from other Kitware projects. Of particular note, the machine setup is completely different. It is getting more and more difficult to maintain the machines since they have all kinds of exceptions on them. We (@brad.king and I) would like to reinstall these machines and sync them up with the rest of our machine setups:
-
abeth -
renar -
umbra
In addition, there are machines still running buildbot jobs:
-
dragnipur -
osheim
that would be also end up being reinstalled (though their other builds would need converted into CI jobs, mainly DIY).
Also of note is that macOS and Windows machines only contain:
- Git installation (with
git-lfs
) - macOS only
- Xcode (macOS only)
- Windows only
- Visual Studio (and relevant toolchains)
- CUDA/NVIDIA drivers
-
sccache
binaries - MSMPI (if needed for a project)
Everything else (including CMake and ninja
) should be downloaded during the CI job so as to avoid having to juggle lots of software installation across many eligible machines.
Full task list:
- Use existing CI machines for existing CI jobs
-
requires using the same tagging strategy used on the rest of the fleet - Linux
-
add NVIDIA hardware tags to existing machines -
disable VTK-m Linux runners to ensure jobs work on the temporary machines -
reinstall VTK-m Linux CI machines
-
-
- Add temporary runners for macOS and Windows to existing machines
- macOS
-
tunja
-
- Windows
-
bop
-
pol
-
- macOS
- Migrate Buildbot configurations to CI jobs
-
dragnipur-release
(macOS) -
dragnipur-debug
(macOS) -
osheim-release
(Windows) -
osheim-debug
(Windows)
-
Cc: @vbolea