-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: Adjust Helm push #25
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
refactor: Adjust Helm push #25
Conversation
| push: ${{ github.event_name == 'push' && github.ref_type == 'tag' }} | ||
| tags: ${{ steps.meta.outputs.tags }} | ||
| labels: ${{ steps.meta.outputs.labels }} |
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.
Run docker/build-push-action@v6
with:
push: false
tags: ghcr.io/diamondlightsource/glazed:latest
From this PR (i.e. non-tag/release run) we would no longer publish on non-tagged commits but still build the container to ensure the Dockerfile is still valid.
The PCT has a stage to run the container and make sure it starts also? Should we have an issue for a command that returns immediately (e.g. glazed --version) to check that the config is preset and the executable is available?
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.
As in an issue to add this as a build step? glazed --version already exists as a command (cargo run -- --version)
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.
Added the build step, see the CI run for this PR
Run docker run --rm test_tag --version
glazed 0.1.0
dan-fernandes
left a comment
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
Making a PR so I can publish from a fork under my own namespace and ensure this behaves how I expect