-
Notifications
You must be signed in to change notification settings - Fork 0
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
[BOP-56] Run CI on merge to main #8
Conversation
workflow_call: | ||
|
||
jobs: | ||
# push-latest: |
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'll uncomment and clean this up when I do the release CI PR
.github/workflows/push-to-ghcr.yml
Outdated
# working-directory: . | ||
# run: make docker-push | ||
|
||
push-dev: |
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.
There is a lot of repeated steps here but doing it this way keeps each of the push jobs independent. The repeated sections are also very quick and don't take long to run.
@@ -0,0 +1,74 @@ | |||
name: Push docker images |
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 was release.yml
. I'll be creating another release.yml
file that reuses this code
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
https://mirantis.jira.com/browse/BOP-56
What this PR does
Adds a CI to run when we merge a PR into main
I set this up to only push an image with the commit SHA. This way dev images are still available in our current registry but anyone using latest wont run into issues. I'll cleanup the release push steps in the followup release CI PR.
Testing
I tested this on my fork of the repo. The push stage didn't work due to credentials but this step was previously working and so I wasn't worried about it.