Use a .ci/cicd-requirements.txt
file to handle CI/CD only dependencies
#8716
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.
Maintainer merge checklist
Component: xxx
label.api-deprecation
orapi-break
label.release-highlight
label to be highlighted in release notes.versionadded
,versionchanged
as needed.Over the past few years it happened multiple times that our CI/CD pipeline started to fail due to unpinned dependencies.
These changes are meant to move all the CI/CD specific dependencies into a separate
requirements
file, to avoid polluting the CI/CD scripts with multiplepip install
statements.This change also allows us to keep these dependencies versions monitored via renovatebot.
Cons:
cicd-requirements.txt
get installed even if something may not be needed in a specific run. We can avoid that by using cached dependencies, however, we're talking about small-sized requirements.