You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub workflow 'Next Dockerimage' runs are silently failing due to an update to docker/build-push-action in devfile/registry-operator#56 to v5.0.0. Any version after v2 uses docker buildx and requires a different setup.
To Reproduce:
Enable actions under folk and try a pushing a commit to the main branch. Workflow should quickly fail before an image is built, under devfile/registry-operator repo runs the image still builds even after failing with the same error.
Expected behavior
Workflow should succeed if secrets are correct. If secrets are unset or incorrect, workflow should still build the image then fail on push with the unauthorized error.
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
Which area this feature is related to?
/kind bug
Which area this bug is related to?
/area registry
What versions of software are you using?
Go project
Operating System and version: N/A
Go Pkg Version: 1.19
Bug Summary
Describe the bug:
GitHub workflow 'Next Dockerimage' runs are silently failing due to an update to
docker/build-push-action
in devfile/registry-operator#56 tov5.0.0
. Any version afterv2
usesdocker buildx
and requires a different setup.To Reproduce:
Enable actions under folk and try a pushing a commit to the
main
branch. Workflow should quickly fail before an image is built, under devfile/registry-operator repo runs the image still builds even after failing with the same error.Expected behavior
Workflow should succeed if secrets are correct. If secrets are unset or incorrect, workflow should still build the image then fail on push with the unauthorized error.
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
Latest run: https://github.com/devfile/registry-operator/actions/runs/6709501591
Additional context
Any workaround?
N/A
Suggestion on how to fix the bug
Revert
docker/build-push-action
to usev1.1.x
versions.The text was updated successfully, but these errors were encountered: