Skip to content

ci: use the chart-owners branch of the charts action - #2654

Draft
nicholasSUSE wants to merge 1 commit into
rancher:mainfrom
nicholasSUSE:ci/chart-owners-action-ref
Draft

nicholasSUSE wants to merge 1 commit into
rancher:mainfrom
nicholasSUSE:ci/chart-owners-action-ref

Conversation

@nicholasSUSE

Copy link
Copy Markdown

Hello! This changes the rancher/charts ship action from a fixed commit to the chart-owners branch, and adds a short comment asking to keep it there.

The commit that was pinned is from before the check that every image of the chart is in the staging registry before the chart is pushed (rancher/charts#9546), so a release from this repository would not run it. Several charts were staged recently with images that were missing from staging, which is what the check prevents.

The next release from this repository will run the check. If an image of the chart is not in stgregistry.suse.com, the job stops before it pushes anything, and the log names the missing images. Please push the images first, then run it again.

Questions are welcome, I'm happy to help.

This workflow called the ship action of rancher/charts at a fixed commit. That
commit is from before the check that every image of the chart is in the staging
registry before the chart is pushed, so releases from this repository did not run
it. The call now uses the chart-owners branch, which carries the checks, and a
comment above it asks to keep it there and not to pin a commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant