👷 Build on GitLab CI - #322
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitLab CI for this repository. The GitLab project
mutationpp/Mutationppmirrors thisone, so a pipeline defined here runs there, with the data directory and test suite we
already know from
.github/workflows/build.yml.This is deliberately the smallest job that proves the wiring: configure and build a
Release tree on Ubuntu 24.04 with CMake. The rest of the migration — the Test matrix
(
ctestwithMPP_DATA_DIRECTORYandLD_LIBRARY_PATH), the Fortran wrapper, thecompiler matrix, and the Python wheels — follows in later merge requests.
Nothing here affects GitHub: the file is inert to Actions and is read only by GitLab.