@Oliver Bertuch I left a comment asking about this:
# Build the application image, but skip the configbaker image (that's a different job)!
Not just for #12772 but because in #12746 I'm also modifying code beneath that comment.
Please see https://github.com/IQSS/dataverse/pull/12772#discussion_r4166104786
@Oliver Bertuch I'm so confused. In https://github.com/IQSS/dataverse/pull/12772#discussion_r4166333927 you seem to be saying the opposite of what the comment says.
I mean, you seem happy with the comment. You don't want to change it. That's fine. Maybe I should just merge the PR. But I'm very confused. :sweat_smile:
Yeah my bad! This is a typo! :zany:
I left a suggestion :see_no_evil:
Cool. Will it break your patch, though?
Please feel free to commit the change. And fix the patch, if necessary.
You mean the backport? No. That patch is applied to the version of the file as contained in the 6.12 tag.
Ah, ok.
You commit. I merge.
I don't think we need to wait for tests to pass. The only change is to a comment.
Done! :check:
Merged! :rocket:
Now what? Run the maintenance job? :thinking: Will that create the configbaker:6.12-noble image?
Just tried that in damp mode. I did forget the detail of having to put backports for configbaker at /modules/container-configbaker/backports/
Stupid me...
Another PR to make and merge, then?
Should be a quick one. Will test by using the branch option of the action.
ok
Sorry for the inconvinience :face_with_peeking_eye:
No worries. It's GitHub Actions. It's expected! ![]()
![]()
That's what I wanna see
![]()
https://github.com/IQSS/dataverse/pull/12776
Merged. I trust you. :smile:
I can put the link to the action run here if that helps...?
Running the maintenance action now! (In normal, non-dry, non-damp mode. https://github.com/IQSS/dataverse/actions/runs/37022260665)
:popcorn:
I see tags on Docker Hub. All done here!
Same. I put a screenshot here: https://github.com/IQSS/dataverse/issues/12761#issuecomment-5955261889
Should we talk in this topic about how my testing failed to discover the missing configbaker image?
Or should we create a new topic?
Dunno. The whole process is a mess. But what we do is also complicated in general. So I don't blame you. I should have run the maintenance script in damp mode myself. Maybe we can add that to the CI workflow, making sure such things get noticed.
On the other hand: maybe it's time to really start thinking about branching off the whole images business. That's certainly not a topic for this thread.
Well, for now, I'll just leave a link to what I did: https://dataverse-guide--12725.org.readthedocs.build/en/12725/developers/making-releases.html#test-docker-images
Unmerged. From #12725. Review and commits welcome!
Oh you meant during the release process!
yeah
Left a suggested edit
committed, thanks
Should there be a screenshot or two?
![]()
![]()
Meh. Screenshots. I vote no.
I was more thinking that instead of just checking for "latest" the person should check for 6.12-noble or whatever as well.
![]()
I was obsessed with "latest" when I wrote that. See
anyway, yes, messy :smile:
but better than nothing!
Last updated: Oct 02 2026 at 18:51 UTC