Skip to content
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

docker-build-and-push-main is failing #4879

Closed
xmfcx opened this issue Jun 17, 2024 · 4 comments
Closed

docker-build-and-push-main is failing #4879

xmfcx opened this issue Jun 17, 2024 · 4 comments
Assignees
Labels
type:bug Software flaws or errors. type:ci Continuous Integration (CI) processes and testing. type:containers Docker containers, containerization of components, or container orchestration.

Comments

@xmfcx
Copy link
Contributor

xmfcx commented Jun 17, 2024

image

docker-build-and-push-main CI started failing after this was merged:

ERROR: tag is needed when pushing to registry
Error: buildx bake failed with: ERROR: tag is needed when pushing to registry

https://github.com/autowarefoundation/autoware/actions/runs/9516216183/job/26232045461#step:8:1288

@oguzkaganozt

Probabable cause

It has passed the test on the initial PR description:

Then, some tag related things were changed within the PR review process:
#4849 (comment)

To prevent such cases from happening, perform the tests again before merging.

Originally posted by @xmfcx in #4849 (comment)

@xmfcx xmfcx added type:ci Continuous Integration (CI) processes and testing. type:containers Docker containers, containerization of components, or container orchestration. labels Jun 17, 2024
@xmfcx
Copy link
Contributor Author

xmfcx commented Jun 17, 2024

@youtalk @oguzkaganozt @mitsudome-r I'll now start working on this task.

@xmfcx xmfcx added the type:bug Software flaws or errors. label Jun 17, 2024
@xmfcx
Copy link
Contributor Author

xmfcx commented Jun 17, 2024

The test on the PR description passed:

But the workflow triggered by the commit pushed failed:

They use docker-build-and-push/action.yaml action.

The biggest difference I see between them is,

  • workflow_dispatch triggered workflow that has passed, allow-push=false
  • push to main triggered workflow that has passed, allow-push=true
Trigger allow-push Workflow Status
workflow_dispatch false
push to main true

So the test doesn't cover the allow-push=true case.

I will investigate further.

@xmfcx
Copy link
Contributor Author

xmfcx commented Jun 19, 2024

https://github.com/autowarefoundation/autoware/actions/runs/9577390080

Still failing.

@xmfcx xmfcx reopened this Jun 19, 2024
@xmfcx
Copy link
Contributor Author

xmfcx commented Jun 19, 2024

Since we no longer trigger this by the push event, it shouldn't be an issue anymore.

@xmfcx xmfcx closed this as completed Jun 19, 2024
@mitsudome-r mitsudome-r moved this to Done in Autoware Labs Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Software flaws or errors. type:ci Continuous Integration (CI) processes and testing. type:containers Docker containers, containerization of components, or container orchestration.
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants