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

Why two different ways to build? #262

Closed
phire-tc opened this issue Dec 27, 2024 · 4 comments
Closed

Why two different ways to build? #262

phire-tc opened this issue Dec 27, 2024 · 4 comments

Comments

@phire-tc
Copy link

Hi! While making the changes for #261 I noticed that the awx-ee actions build the container image in two different ways. I'm curious why that is.

ci.yml and release.yml use tox to build. This takes roughly 10 minutes.

build-latest.yml, on the other hand, uses docker buildx to build. This takes roughly 50 minutes.

If this is just an oversight I'd be happy to update build-latest.yml so it, too, uses tox (and will build 5 times faster).

@kurokobo
Copy link

The build-latest.yml is designed to build images for both AMD64 and ARM64 architectures. It takes a long time, but most of that time is probably spent on the ARM64 build.

@phire-tc
Copy link
Author

Thank you for the info, that makes sense. In that case are the awx-ee release builds not made by release.yml? release.yml appears to build amd64-only whereas the awx-ee release images on quay.io are both amd64 and arm64. How were the releases generated?

@kurokobo
Copy link

kurokobo commented Jan 4, 2025

You can see the actual history for each workflows here: https://github.com/ansible/awx-ee/actions
Additionally, please pay attention to on in each workflows. The release.yml is designed to be triggered by on.release, so it has never actually been used. The actual builds are entrusted to build-latest.yml, which runs automatically on a regular basis.

@phire-tc
Copy link
Author

phire-tc commented Jan 6, 2025

Ah, so there's some external process for making releases and release.yml is a red herring. Thank you for the info!

@phire-tc phire-tc closed this as completed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants