-
Notifications
You must be signed in to change notification settings - Fork 325
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
workflow: don't push Docker container on PR #2984
workflow: don't push Docker container on PR #2984
Conversation
The docker container on PR action is broken in case the PR is not opened within the Gluon project. Remove the build on PR so the pipeline does not fail for third party PRs. Signed-off-by: David Bauer <[email protected]>
Hmm, optimally, we'd build the container (so the build is checked for PRs), but don't attempt to push it. Not sure if there is any simple way to achieve that. |
Something like the following? (sorry, github doesn't allow to do this as a suggestion)
Hoewer, this is only one potential half of what's required. In a fork the action would still fail because the destination of the push is still hardcoded. |
Hmm, maybe it would even be possible to set the value of |
I'd remove it for now so the CI won't complain. Can someone create a PR with the suggested changes so we can verify they work as expected? |
The docker container on PR action is broken in case the PR is not opened within the Gluon project. Remove the build on PR so the pipeline does not fail for third party PRs. Signed-off-by: David Bauer <[email protected]> (cherry picked from commit 9577d2f) Signed-off-by: Tom Herbers <[email protected]>
The docker container on PR action is broken in case the PR is not opened within the Gluon project. Remove the build on PR so the pipeline does not fail for third party PRs. Signed-off-by: David Bauer <[email protected]>
The docker container on PR action is broken in case the PR is not opened within the Gluon project.
Remove the build on PR so the pipeline does not fail for third party PRs.