pipeline: config: split config in multiple files #1054
Merged
Conversation
This file contains 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
Contributor
padovan
commented
Feb 27, 2025
padovan
commented
pawiecz
reviewed
Feb 27, 2025
|
#914 has been adjusted and merged - sorry it requires another rebase of this PR. Once the main file is finally split there should be less conflicts and less overall friction with the Pipeline config refactoring. |
The config grew to an unmanageable size, so let's split it into multiple files. Note: "config/pipeline.yaml" was mentioned in results_summary service, but that services doesn´t use configs at all. Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com>
padovan
force-pushed
the
split-pipeline-config
branch
from
d1a142b to
65a38be
Compare
|
Tested on staging, thanks ! |
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.