Bookworm migration for all dependency packages in azurepipeline for sonic-mgmt-framework #132
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
…d brought in the module versions accordingly
…/http/httptest/recorder.go-checkWriteHeaderCode()
Merged
9 tasks
kwangsuk
approved these changes
Apr 19, 2024
|
Ping @sachinholla for review |
sachinholla
approved these changes
Apr 22, 2024
saiarcot895
approved these changes
Apr 22, 2024
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.
Why I did it
As part of the migration of sonic-mgmt-framework repo to bookworm distro, migrating the azure-pipeline to refer to the bookworm build for dependency package installation.
How I did it
Changed all references from buster to bookworm in azure-pipeline for dependency package installation.
How to verify it
Built the mgmt-framework docker and executed the azure pipeline unit tests locally.