-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add GitHub Action for building and pushing UI and BFF images #446
Conversation
a93f77d
to
3e9902a
Compare
3e9902a
to
0e98ea4
Compare
My user must not have access to the creds for the kubeflow docker so I'm assuming there's no way to test this without having the bot do it on push to main? @tarilabs any ideas how I can test? |
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.
My user must not have access to the creds for the kubeflow docker so I'm assuming there's no way to test this without having the bot do it on push to main? @tarilabs any ideas how I can test?
When I face similar situation @Griffin-Sullivan , I did setup DOCKERHUB_USERNAME
etc in my GitHub repo (my fork) and updated IMG_ORG
to point at my username in dockerhub.io
It also gives you an idea/survey of the changes we will need to apply midstream (kind request: please remind me/us when this PR will be synchronized midstream!)
edit: for a better "survey", I recommend also checking which changes are required for using quay.io
instead of dockerhub: that is typically about setting one more env variable AND someIMG:
in the GHA update.
This will be handy not only for midstreams but also when eventually we will publish to ghcr in addition to dockerhub for this upstream
@@ -0,0 +1,94 @@ | |||
name: Build and Push UI and BFF Images | |||
on: | |||
pull_request: |
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.
I appreciate in the PR description is mentioned this on: pull_request
is only for testing, but I'd rather make a comment so to make sure we don't forget before merging 😅
c3bd640
to
03d0046
Compare
03d0046
to
c5bceac
Compare
You can see on https://github.com/Griffin-Sullivan/model-registry/actions/runs/11147635638/job/30982430523?pr=1 that the Action is passing when I push to my own quay repo. You can find them here: https://quay.io/user/gsulliva/?tab=repos The reason the build-and-test-image action is failing is because I'm forcing the build script to run with |
jobs: | ||
build-image: | ||
runs-on: ubuntu-latest | ||
environment: griffin-testing # TODO: REMOVE LINE BEFORE MERGING |
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.
Just an extra reminder this line is here :D
scripts/build_deploy.sh
Outdated
@@ -3,7 +3,7 @@ | |||
set -e | |||
|
|||
# see Makefile for the IMG_ variables semantic | |||
IMG_REGISTRY="" | |||
IMG_REGISTRY="quay.io" # TODO: CHANGE TO EMPTY STRING BEFORE MERGE!!! |
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.
Another reminder :D
Looks good, I haven't completely groked the logic but the general tasks all look good! |
c5bceac
to
bcfe41b
Compare
Latest run is still passing on https://github.com/Griffin-Sullivan/model-registry/actions/runs/11162537114/job/31027401589?pr=1. If someone will review this I can remove all the TODOs 😄 |
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.
I think it's worthy to remove the TODOs
/lgtm
shell: bash | ||
env: | ||
IMG_REPO: ${{ env.IMG_UI_REPO }} | ||
IMG: ${{ env.IMG_ORG }}/${{ env.IMG_UI_REPO }} |
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.
this IMG
will need to be prefixed with quay.io
for midstream, correct?
I'm thinking if we should just be explicit and introduce docker.io/
prefix in all GHAs 🤔
what is your team thought here?:
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.
So I discussed with @lucferbux and @alexcreasy, and the current plan for midstream is to combine the UI here with the midstream image for the dashboard using webpack. That means we don't need a separate image for Model Registry UI and it will only be used for upstream.
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.
ack! thanks for the update
Signed-off-by: Griffin-Sullivan <[email protected]>
bcfe41b
to
ece639b
Compare
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.
/lgtm
@tarilabs we need you to merge this one! |
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.
All looks good to me.
@tarilabs would you mind approving this, if you're happy with the changes? It's outside my or Eder's jurisdiction :) |
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexcreasy, ederign, tarilabs 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 |
thanks @tarilabs |
Signed-off-by: Matteo Mortari <[email protected]>
Description
Added a GH Action for building and pushing the UI and BFF images. Reuses the build script for Model Registry server, and edits the Makefile a little bit to get everything working. I also turned off image builds for MR server when a PR is being made only for UI / BFF changes. I can remove that if we want to keep building them.
How Has This Been Tested?
Going to test the PR as
on: pull_request
then if it passes will update the PR to run the actionon: push
.Merge criteria:
DCO
check)If you have UI changes