-
Notifications
You must be signed in to change notification settings - Fork 488
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
Tag version for the container base image #10478
Labels
Component: Containers
Anything related to cloudy Dataverse, shipped in containers.
Type: Feature
a feature request
Milestone
Comments
poikilotherm
added
Type: Feature
a feature request
Component: Containers
Anything related to cloudy Dataverse, shipped in containers.
labels
Apr 10, 2024
2024/07/19 - 6.4 proposal request from @poikilotherm |
pdurbin
added
the
Champion: pdurbin
Championed by @pdurbin for inclusion in the next release
label
Jul 19, 2024
7 tasks
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 17, 2024
We will deal with shipping the updated application container images separately as part of issue IQSS#10618. Adding some comments about why some stuff is still around.
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 17, 2024
Now adding the "upcoming" tag during the develop branch run. Also some reorganizing to ship the tag options using outputs, not env vars. Moving the common Maven option to enable tag overrides to the command instead of the options building.
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 17, 2024
Now adding the "upcoming" tag during the develop branch run. Also some reorganizing to ship the tag options using outputs, not env vars. Moving the common Maven option to enable tag overrides to the command instead of the options building.
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 17, 2024
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
Re-enable and change everything necessary to reference the upstream IQSS context as of now.
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
Re-enable and change everything necessary to reference the upstream IQSS context as of now.
poikilotherm
added a commit
to gdcc/wip-dataverse-base-image
that referenced
this issue
Sep 19, 2024
pdurbin
removed
the
Champion: pdurbin
Championed by @pdurbin for inclusion in the next release
label
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: Containers
Anything related to cloudy Dataverse, shipped in containers.
Type: Feature
a feature request
Overview of the Feature Request
People are sometimes struggling with the base image when building the application image. When there are changes pushed to the unstable tag, sometimes people still use a cached version and run into problems.
What existing behavior do you want changed?
We should tag the base image with some versioning scheme and make the application image use the tag by default. That way people will receive newer base image versions automatically.
Any open or closed issues related to this feature request?
More discussion here: https://dataverse.zulipchat.com/#narrow/stream/375812-containers/topic/change.20version.20scheme.20base.20image.3F
The text was updated successfully, but these errors were encountered: