[puppetsync] Fix tag-triggered RPM builds and harden tag_deploy - #89
Merged
michael-riddle merged 1 commit intoAug 13, 2026
Merged
Conversation
Every tag push has been dispatching two release_rpms.yml runs hardcoded to the retired centos7/centos8 build containers, so all tag-triggered RPM builds fail. tag_deploy.yml now dispatches once with no OS override, and release_rpms.yml builds el8/el9/el10 from a single build_container_oses input (narrowable on manual runs), with release resolution split into its own job so the parallel per-OS legs cannot race on release creation or asset wipes. tag_deploy.yml also now surfaces the Puppet Forge API response when a publish fails (instead of curl --fail discarding it) and keeps the built module archive as a workflow artifact and release asset.
michael-riddle
approved these changes
Aug 13, 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
3 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.
Every tag push has been dispatching two release_rpms.yml runs
hardcoded to the retired centos7/centos8 build containers, so all
tag-triggered RPM builds fail. tag_deploy.yml now dispatches once
with no OS override, and release_rpms.yml builds el8/el9/el10 from
a single build_container_oses input (narrowable on manual runs),
with release resolution split into its own job so the parallel
per-OS legs cannot race on release creation or asset wipes.
tag_deploy.yml also now surfaces the Puppet Forge API response when
a publish fails (instead of curl --fail discarding it) and keeps
the built module archive as a workflow artifact and release asset.