-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve docker build workflow in forks #337
Conversation
Instead of using hardcoded image name, take it from the repo name. This makes it work well for forks.
🚀 e2e tests runWe add labels to the PRs to control the e2e test runs by running specific tests and skipping some test contexts,
ℹ️ Ask a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's better to keep this in your Fork.
our repo will not change for now.
@mcbenjemaa i have to disagree with you here. I think the proposed change makes a lot of sense, since it allows contributors to more easily verify their changes in their repos, before submitting them to us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@isZumpo can you check the actionlint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just this minor thing. Aside from that, I'm happy for this to go in.
Quality Gate passedIssues Measures |
Glad to see that the PR managed to get positive feedback and fixes commited and even a merge. All while I was away at work. Great work and thanks to everyone 😁 |
Description of changes:
When forking the repository for development purposes, the github action workflow inside the fork will try upload the built image to ghcr.io/ionos-cloud/cluster-api-provider-proxmox, which results in a permission error:
ERROR: denied: permission_denied: The requested installation does not exist.
This can be avoided by instead of having a hardcoded image name in the workflow, one dynamically takes the GITHUB_REPOSITORY variable and converts it into lowercase (for those who have Github usernames with one or more capital letters). Consequentially, every fork will push to its own registry without permission issues, while the main repository keeps working just like before.
Testing performed:
Verified workflow in my fork. It manages to publish ghcr images to my fork/registry.