enh(delivery): promote pulp content by href instead of re-uploading - #6367
Merged
Conversation
MON-207621: testing and stable share their domain since the merge, so the promotion associates the testing content hrefs directly with the stable repository — the per-package re-download/re-upload is gone (rpm entirely; deb keeps only the legacy first-per-arch upload that establishes the release component). Packages keep their delivery-time labels.
kduret
requested review from
mushroomempires and
tuntoja
and removed request for
a team
August 21, 2026 13:24
mushroomempires
approved these changes
Aug 21, 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
2 participants
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.
Description
Fixes: MON-207621
CI/delivery-only change. Since the pulp domain merge (MON-207474), testing and stable share their domain and content units: the promotion now associates the testing content hrefs directly with the stable repository instead of re-downloading and re-uploading every candidate (rpm: no transfer at all; deb: only the legacy first-per-arch upload remains, establishing the release component). Packages keep their delivery-time labels.
Type of change
How this pull request can be tested ?
On the dev pulp stack: deliver plugins to testing then promote to stable and check the promote job transfers no package payload while the post-promote verification stays green.