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

Push generic images on release and on master #3104

Merged
merged 3 commits into from
Jan 8, 2025
Merged

Push generic images on release and on master #3104

merged 3 commits into from
Jan 8, 2025

Conversation

Itxaka
Copy link
Member

@Itxaka Itxaka commented Jan 7, 2025

also renames the jobs so they are easily identificable from the CI web

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

also renames the jobs so they are easily identificable from the CI web

Signed-off-by: Itxaka <itxaka@kairos.io>
@Itxaka Itxaka requested a review from a team January 7, 2025 11:14
Signed-off-by: Itxaka <itxaka@kairos.io>
@Itxaka Itxaka changed the title Push generic images on release Push generic images on release and on master Jan 7, 2025

sudo mv build release
- name: Push to quay
--VARIANT=${{ matrix.variant }}
Copy link
Member

Choose a reason for hiding this comment

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

no k3s versions anymore? then variant can be fixed to "core"

Copy link
Member Author

Choose a reason for hiding this comment

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

on release no, at least for generic and now, as we dont know how useful they are gonna be I rather not push so much shit for no reason. Base images are good currently, but I expect this to change to standard at some poitn if arm takes off.

build-arm-generic:
needs:
- get-core-matrix-generic
runs-on: ARM64
Copy link
Member

Choose a reason for hiding this comment

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

how about putting this whole section in a reusable? I'm assuming is the same to build for PR vs master, etc but maybe I'm missing something

Copy link
Member Author

Choose a reason for hiding this comment

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

kind of yeah, but I wanted to test that it worked first before reqorking into a reusable job, or even reusing the existing one to build the docker images and create isos IF needed, as I dont think we should create isos/raw images from the arm stuff, just the base containers which then you can transform to an iso/raw image for your board

Signed-off-by: Itxaka <itxaka@kairos.io>
@Itxaka
Copy link
Member Author

Itxaka commented Jan 8, 2025

lets see how it breaks :D

@Itxaka Itxaka merged commit 885c0eb into master Jan 8, 2025
44 of 46 checks passed
@Itxaka Itxaka deleted the arm_push branch January 8, 2025 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants