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

chore(ci): build multiplatform next container image #2036

Merged

Conversation

kadel
Copy link
Member

@kadel kadel commented Dec 2, 2024

Description

This updates the build process for the next image (build from main branch)

It adds the arm64 image build. arm64 and amd64 are built in parallel.

Platform specific images are tagged with next-{platform}. This is mainly to make the amd64 image available quickly (takes less than 40 min) for testing, as arm64 build can take 4 hours.

After both builds are done, the next multiplatform tag is pushed and can be used.

Screenshot 2024-12-02 at 14 50 21 Screenshot 2024-12-02 at 14 52 13

Which issue(s) does this PR fix

@kadel kadel requested a review from a team as a code owner December 2, 2024 14:38
Copy link
Contributor

github-actions bot commented Dec 2, 2024

@nickboldt
Copy link
Member

Do we want PR builds on arm too, in case you're developing something locally on your arm64 mac?

@kadel
Copy link
Member Author

kadel commented Dec 4, 2024

Do we want PR builds on arm too, in case you're developing something locally on your arm64 mac?

I'm working on that as well. I'll do it in a separate PR. e2e tests depend on those images, so I want to make sure that they are not delayed by arm image builds

@kadel kadel mentioned this pull request Dec 5, 2024
5 tasks
Copy link
Contributor

@kadel kadel requested a review from rhdh-qe December 19, 2024 11:23
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Copy link
Contributor

github-actions bot commented Jan 7, 2025

@kadel kadel force-pushed the build-multiplatform-next-image branch from 5d6bfc1 to fbed803 Compare January 7, 2025 16:46
Copy link
Contributor

github-actions bot commented Jan 7, 2025

@kadel kadel force-pushed the build-multiplatform-next-image branch from fbed803 to 7b9d684 Compare January 9, 2025 12:52
Copy link
Contributor

github-actions bot commented Jan 9, 2025

@@ -76,6 +68,7 @@ jobs:
# to autodelete PR image tags, set an expiry date
imageLabels: quay.expires-after=14d
push: true
platform: linux/amd64
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so PR builds are single-arch but next builds are dual-arch? 🤔 What if your contributor is on a Mac and wants to test their PR build?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, for now yes.

My plan is to do the PR images in followup PR.
As it will require small updates to e2e tests as well.
e2e tests should not wait for the whole multiplatform image to be built, as it can take 4+ hours. So we will need to reconfigure them to wait for the platform specific tag.

@kadel kadel force-pushed the build-multiplatform-next-image branch from 76c02be to 36bda1f Compare January 14, 2025 14:08
@nickboldt
Copy link
Member

nickboldt commented Jan 14, 2025

lasr PR build failed with

ERROR: failed to solve: failed to push quay.io/rhdh-community/rhdh:pr-2036: failed to copy: unexpected status from PUT request to https://quay.io/v2/rhdh-community/rhdh/blobs/uploads/9a90c668-b180-4b0d-b97c-c01d71271356?digest=sha256%3A8b76ee4a0a25c4b269af66290f7fdb1d0c56383c3c67d60a32778039bb0f0a28: 413 Request Entity Too Large

Previous build worked 5 days ago at https://quay.io/repository/rhdh-community/rhdh?tab=tags&tag=pr-2036 so either this is a transient glith w/ quay.io or you made the image too big?

@kadel kadel force-pushed the build-multiplatform-next-image branch from 36bda1f to 2c1d63d Compare January 15, 2025 11:21
@kadel
Copy link
Member Author

kadel commented Jan 16, 2025

@nickboldt can you give this another look?

Copy link

openshift-ci bot commented Jan 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nickboldt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nickboldt nickboldt added the lgtm label Jan 16, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 350a58b into redhat-developer:main Jan 16, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants