docker/kcidb: fix logspec to a specific version #911
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
Some cases will require the kcidb bridge to interpret results from logspec before creating issues and incidents. Fix logspec to a specific commit so we can control when to upgrade it. This allow us to upgrade logspec in the same commit we upgrade kcidb bridge to keep them in sync. Signed-off-by: Helen Koike <[email protected]>
JenySadadia
approved these changes
Nov 25, 2024
|
@nuclearcat o/ please review and merge this if possible |
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.
Some cases will require the kcidb bridge to interpret results from logspec before creating issues and incidents. Fix logspec to a specific commit so we can control when to upgrade it. This allow us to upgrade logspec in the same commit we upgrade kcidb bridge to keep them in sync.