-
Notifications
You must be signed in to change notification settings - Fork 26
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
Container image building and publishing #23
Conversation
Codecov Report
@@ Coverage Diff @@
## main #23 +/- ##
==========================================
- Coverage 97.10% 96.00% -1.11%
==========================================
Files 4 4
Lines 415 425 +10
==========================================
+ Hits 403 408 +5
- Misses 8 11 +3
- Partials 4 6 +2
Continue to review full report at Codecov.
|
a76d900
to
5d7f71c
Compare
5d7f71c
to
4e48894
Compare
4e48894
to
ba0f923
Compare
Allows users to run ipxedust in a container. Signed-off-by: Jacob Weinstock <[email protected]>
This uses goreleaser to build and push container images to quay.io for multiple architectures. Signed-off-by: Jacob Weinstock <[email protected]>
ba0f923
to
4632a43
Compare
@@ -16,7 +16,7 @@ jobs: | |||
- name: Install Go | |||
uses: actions/setup-go@v2 | |||
with: | |||
go-version: "1.17" | |||
go-version: "1.17.5" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to lock this?
This is super old. Is it still relevant? |
It is definitely old. It needs a revisit code wise (merge main, possibly update versions, etc) and i'd still like to see it incorporated. |
no cycles for this. will re-open if/when i do. |
Description
This enables building and publishing container images to quay.io/tinkerbell. GitHub actions and Goreleaser are set up to create and publish container images based on Git tags.
This could potentially be an example repo for how we could handle versioning. See proposal 0002.
CC: @displague
Why is this needed
Fixes: #22
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: