ci: Use additional files and reference tags for CI setup #120
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
github-actions
bot
added
the
ci
|
Closes #119. |
gregjacobus
approved these changes
Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This moves the anchors used for setup into a separate file
.gitlab/ci/setup.yml(and converts them to references). This allows other GitLab repositories to include that YAML file directly instead of including the main.gitlab-ci.ymlfile and then needing to override or otherwise negate jobs that should not be run.I also changed a couple of the job names and removed the
virtualenvdependency for Docker-based jobs in order to reuse a bunch of the references in both the Docker-based jobs (docs, pages, build, deploy) and the ones running in a native runner (performance). I didn't see an obvious reason that we neededvirtualenvbeyond Python's built-invenv, and it didn't play nicely with the native runner. If it is a requirement, I'll find a workaround.