ci: support Prime registry image publishing - #222
Merged
Merged
Conversation
bk201
marked this pull request as ready for review
August 20, 2026 07:17
|
Tick the box to add this pull request to the merge queue (same as
|
brandboat
reviewed
Aug 24, 2026
brandboat
left a comment
Member
There was a problem hiding this comment.
What about using matrix? Doing this can simplify the workflow in my opinion
brandboat
approved these changes
Aug 24, 2026
Use shared harvester-actions to select and authenticate the appropriate registry for each build type. Publish node-manager and webhook images to Docker Hub, staging, or Prime based on the release tag, and normalize prime-prefixed image tags. Signed-off-by: Kiefer Chang <kiefer.chang@suse.com>
Signed-off-by: Kiefer Chang <kiefer.chang@suse.com>
brandboat
approved these changes
Aug 24, 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.
Use shared harvester-actions to select and authenticate the appropriate registry for each build type.
Publish node-manager and webhook images to Docker Hub, staging, or Prime based on the release tag, and normalize prime-prefixed image tags.
Related Issue(s):
https://github.com/harvester/suse-virtualization-mgmt/issues/12
Test plan:
Additional documentation or context