workflows: build a multi-arch tasks container #603
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note: this doesn't push a |
allisonkarlitskaya
force-pushed
the
buildjet
branch
2 times, most recently
from
67449b2 to
2a006cb
Compare
allisonkarlitskaya
had a problem deploying
to
quay.io
GitHub Actions
Failure
allisonkarlitskaya
had a problem deploying
to
quay.io
GitHub Actions
Error
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
had a problem deploying
to
quay.io
GitHub Actions
Failure
allisonkarlitskaya
force-pushed
the
buildjet
branch
from
2a006cb to
7528457
Compare
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
had a problem deploying
to
quay.io
GitHub Actions
Failure
allisonkarlitskaya
force-pushed
the
buildjet
branch
2 times, most recently
from
a458141 to
8f3d245
Compare
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
allisonkarlitskaya
temporarily deployed
to
quay.io
GitHub Actions
Inactive
|
Out of all of the things that I thought might be difficult, I didn't imagine that it would be getting the Anyway — this is working, and we now have a |
martinpitt
reviewed
Mar 15, 2024
There was a problem hiding this comment.
This looks great, thanks for figuring out all the details!
I'm a bit concerned about the integration test failure -- although it's not quite clear what this has to do with setting an empty LOG_MATCH. As a first thing, perhaps you could do a no-change force-push to run them again? (We can't just retry as the "unit-tests" context already exists).
Build a tasks container for arm64 in addition to amd64. We do this by splitting the build process into multiple jobs. For the arm one, we make use of the arm runners from BuildJet. At the end, we write the manifest and upload that with the "public" tag name. Remove the local infrastructure and rules for pushing the container; it's not so easy anymore.
allisonkarlitskaya
force-pushed
the
buildjet
branch
from
8f3d245 to
3c5b888
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build a tasks container for arm64 in addition to amd64.
We do this by splitting the build process into multiple jobs. For the arm one, we make use of the arm runners from BuildJet. At the end, we write the manifest and upload that with the "public" tag name.
I kicked off a workflow run, which produced the 2024-03-15 tag on quay:
I'm taking that for a spin now in cockpit-project/starter-kit#812