Repository navigation
The Docker upgrade jobs compared versions against hand-kept tables in - #176
Merged
Merged
Conversation
ppg-testing, which drift every time OBS bumps a component. An upgrade entry lives in a common project and tests two images from two projects, so the list computed from the entry's own project was the first major in its paths (PG 18 for the common container projects) -- wrong for a 16 -> 17 upgrade in both phases, and no single list can be right for both (percona-postgresql and percona-pgaudit differ). _resolve_lane_images now records, before resolving, the projects the entry's image references name (_image_projects; entry-level, so it never reaches a job's parameters). For an entry with an OLD_REPOSITORY project, EXPECTED_VERSIONS is computed from the new image's project (NEW_REPOSITORY, else REPOSITORY) and the new OLD_EXPECTED_VERSIONS from OLD_REPOSITORY's, with the same OBS-built versions as for a server entry of each project. They are computed before the conflict check, so a version conflict in either image's project blocks the upgrade entry like one in the lane's own packages. Values set in the entry are kept.
mohitj1988
force-pushed
the
fix_expected_version_for_upgrade
branch
from
October 20, 2026 12:33
eebd16d to
83f3035
Compare
rjd15372
approved these changes
Oct 20, 2026
This file contains hidden or 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
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.
ppg-testing, which drift every time OBS bumps a component. They could not use EXPECTED_VERSIONS: an upgrade entry lives in a common project and tests two images from two projects, so the list computed from the entry's own project was the first major in its paths (PG 18 for the common container projects) -- wrong for a 16 -> 17 upgrade in both phases, and no single list can be right for both (percona-postgresql and percona-pgaudit differ).
_resolve_lane_images now records, before resolving, the projects the entry's image references name (_image_projects; entry-level, so it never reaches a job's parameters). For an entry with an OLD_REPOSITORY project, EXPECTED_VERSIONS is computed from the new image's project (NEW_REPOSITORY, else REPOSITORY) and the new OLD_EXPECTED_VERSIONS from OLD_REPOSITORY's, as for a server entry of each project. Values set in the entry are kept.