-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: add VERSION to ci-base-image #1735
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.
See my comment for .github/workflows/publish-dev-ci-base-image.yml
.
feffb49
to
1ac5b4b
Compare
@@ -81,6 +81,7 @@ jobs: | |||
name: Publish CI Base Image | |||
env: | |||
IMAGE_NAME: ci-base-image | |||
IMAGE_VERSION: 1.0.0 |
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.
nice
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 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 👍🏻
# Goal The goal of this PR is to publish the 1.0.0 version of ci-base-image. # Discussion Due to a typo in `merge-pr.yml`, #1735 failed to publish a new version of `ci-base-image`. This PR touches `ci-base-image.dockerfile` to trigger the `publish-ci-base-image` github action workflow. Co-authored-by: Matthew Orris <--help>
Goal
The goal of this PR is to add a version to the
ci-base-image
container when it is published to DockerHub.IMAGE_VERSION
is added to the publishing jobs and stored as aLABEL
in the container itself.IMAGE_VERSION
will be baselined as1.0.0
docker inspect
can be used to check the version of a container and should be in-sync with the tag version.A follow on PR will be used to update the github workflows to use the version number.
Discussion
The current workflows pull using the defaults, which is the
latest
tag.Adding a version will allows us better traceability and better maintenance moving forward.