<WIP>Bookworm migration for all dependency packages in azurepipeline for sonic-gnmi #210
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
ranjinidn
force-pushed
the
bookworm_migration_sonic_gnmi
branch
from
5f54f80 to
33feef4
Compare
…sonic-gnmi into bookworm_migration_sonic_gnmi
ranjinidn
changed the title
ranjinidn
force-pushed
the
bookworm_migration_sonic_gnmi
branch
from
e50fe45 to
eccd358
Compare
|
|
ranjinidn
force-pushed
the
bookworm_migration_sonic_gnmi
branch
from
12cceec to
104e19f
Compare
ranjinidn
force-pushed
the
bookworm_migration_sonic_gnmi
branch
from
104e19f to
382fa9e
Compare
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-gnmi repo to bookworm, migrating the azure pipeline files to refer to the bookworm build for dependency installation.
How I did it
Changed all references from bullseye to bookworm in azure-pipeline for dependency packages installation.
How to verify it
The tests in azurepipeline were run on the bookworm build locally and has the same behavior as bullseye build.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)