-
Notifications
You must be signed in to change notification settings - Fork 27
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
Only push the production container when the release was cut #1077
Only push the production container when the release was cut #1077
Conversation
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.
Is there a way to be even more specific here? I imagine that /any/ workflow call (even those that aren't for release) would trigger this if
.
Also, is there a world in which you'd want workflow_dispatch
to trigger a push?
Good call. I pass a variable from the |
@@ -192,7 +194,7 @@ jobs: | |||
with: | |||
context: . | |||
file: ./images/Dockerfile | |||
push: ${{ github.repository == 'PelicanPlatform/pelican' && github.event_name != 'pull_request' }} | |||
push: ${{ github.repository == 'PelicanPlatform/pelican' && (inputs.release_workflow || false) }} |
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.
What's with the || false
here? Kinda seems superfluous?
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.
it does look superfluous but otherwise the yaml check will fail when the workflow was not triggered by the workflow call (in which case release_workflow
is undefined) and gives the error:
Error: Input does not meet YAML 1.2 "Core Schema" specification: push
Support boolean input list: `true | True | TRUE | false | False | FALSE`
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.
One question but otherwise LGTM. Pre-approving.
8fbbeff
to
b1d2e45
Compare
This should fix the critical bug described in #1075 but leave the part untouched where "automatically tagging the latest release with the largest semantic version as the latest"