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

Build and push quarry image #1

Merged
merged 4 commits into from
Oct 16, 2023
Merged

Build and push quarry image #1

merged 4 commits into from
Oct 16, 2023

Conversation

vivian-rook
Copy link
Contributor

@vivian-rook vivian-rook commented Sep 2, 2022

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

A github action to build and push the quarry container image to quay.io.

Bug: T316958
Comment on lines 13 to 21
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 }}
Copy link
Collaborator

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.

Copy link
Contributor Author

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.

Copy link
Collaborator

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.

T316958 Outdated Show resolved Hide resolved
siddharthvp
siddharthvp previously approved these changes Oct 16, 2023
@vivian-rook vivian-rook merged commit 30638f0 into main Oct 16, 2023
2 checks passed
@vivian-rook vivian-rook deleted the T316958 branch October 16, 2023 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants