-
Notifications
You must be signed in to change notification settings - Fork 10
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
Build and push quarry image #1
Conversation
A github action to build and push the quarry container image to quay.io. Bug: T316958
with: | ||
repository: ${{ github.event.pull_request.head.repo.full_name }} | ||
|
||
- name: git fetch | ||
run: | | ||
git fetch | ||
- name: git checkout | ||
run: | | ||
git checkout ${{ github.head_ref }} |
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.
no need to do any of this - just uses: actions/checkout@v4
is enough for it to check out the branch from the PR.
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.
Neat! Does this work with an outside contributor off of a fork? I guess we can merge it and find out.
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.
The checkout would work (i.e. the fork gets checked out). What won't work is accessing the github secrets for docker login.
A github action to build and push the quarry container image to quay.io.
The way the code is structured in the repo has a downside, in that any update to the code will update the container image. It is likely worth moving the code off of the root of the repo into /code/ or the like, then this action can be updated to only trigger when there is a change to something in that directory. Though this will likely cause a lot of busy work until quarry moves to k8s in prod.
For now it updates the image all the time, not the biggest problem, but not the most elegant.
Bug: T316958