Change CI workflows to release tagged container images for Dataverse#11477
Merged
ofahimIQSS merged 66 commits intoIQSS:developfrom Jun 9, 2025
Merged
Change CI workflows to release tagged container images for Dataverse#11477ofahimIQSS merged 66 commits intoIQSS:developfrom
ofahimIQSS merged 66 commits intoIQSS:developfrom
Conversation
poikilotherm
added
Component: Code Infrastructure
poikilotherm
added
Feature: Container Guide
Release
poikilotherm
force-pushed
the
10618-app-image-tags
branch
from
40c2d0e to
53843cc
Compare
cmbz
added
FY25 Sprint 24
poikilotherm
force-pushed
the
10618-app-image-tags
branch
from
da51a39 to
bb0262a
Compare
poikilotherm
force-pushed
the
10618-app-image-tags
branch
3 times, most recently
from
5861f79 to
db86eb1
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
poikilotherm
force-pushed
the
10618-app-image-tags
branch
2 times, most recently
from
aa8e910 to
09518af
Compare
For the base image we didn't use a parent image which has a namespace. If the given image has a namespace, it needs to be removed from the repo string to create the tags lookup URL.
Done because we want to have a similar script for other images as well.
We will add more jobs, so make the job's name more speaking, referring to what happens inside
This is necessary so we can have the maintenance jobs only work on their respective parts and not always do both. Otherwise the configbaker image would have many more fixed tags than necessary (the same as the app image has), confusing people because there were no changes.
We will need it to have the version number ready for the maintenance job. At the same time, leaving a note that we will _not_ use it for the default tag we use during development. If we'd use the version there, too, it would break many scripts that now can rely on the single rolling tag of "unstable", as we'd need to change the tags everywhere for a new version.
Removed temporary testing condition for `gdcc/wip-base-image` and reinstated the `if` condition to restrict workflow runs to the upstream `IQSS` repository.
Introduced documentation detailing the structure, purpose, and usage of the `src/backports` directory to support consistent patch management across multiple Dataverse release versions.
Contributor
Author
|
@pdurbin as requested, I added a README to src/backports |
pdurbin
approved these changes
Jun 4, 2025
Member
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
I'm relying on the testing @poikilotherm did but this looks good to me. Approved.
github-project-automation
bot
moved this from In Review 🔎
to Ready for QA ⏩
in IQSS Dataverse Project
4 tasks
Contributor
|
I reran the failing continuous integration job - it looks like it failed again: https://jenkins.dataverse.org/blue/organizations/jenkins/IQSS-Dataverse-Develop-PR/detail/PR-11477/30/pipeline |
Contributor
|
Looks good on my end. Merging. |
github-project-automation
bot
moved this from QA ✅
to Merged 🚀
in IQSS Dataverse Project
This was referenced Jun 9, 2025
This was referenced Sep 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
People demand container images of Dataverse with tags of released versions of Dataverse.
This PR will meet their demands.
Open TODOs before this is ready for review:
Preview images for base image-> new issue, new dev cycle.Which issue(s) this PR closes:
Special notes for your reviewer:
It needs to be decided if not running the Maven Unit Test workflow on push to master and not on new tags.
Otherwise, this is only touching container stuff, low risk for anyone else.
Suggestions on how to test this:
DRY_RUN=1to avoid building anything orDAMP_RUN=1to see Maven build Docker images but not push them to the Hub. Make sure to call the scripts from the repo's root via./.github/workflows/scripts/containers/maintain-YYY.sh <branch names you want included>Does this PR introduce a user interface change? If mockups are available, please link/include them here:
None.
Is there a release notes update needed for this change?:
🔋 included
Additional documentation:
Preview docs at https://dataverse-guide--11477.org.readthedocs.build/en/11477/container/index.html