In #12498 Jim made a PR to bump the version of Payara but CI is failing for both API tests and JSF tests:
![]()
@Ash Manda @Oliver Bertuch any ideas?
The error is Unable to pull 'gdcc/base:6.12-noble-p7.2026.7-j21'.
![]()
For some context, and history, I suppose, in the past, when we made upgrades of Payara during the Jenkins era, @Don Sizemore would often set up a dedicated job and server for us. We'd get the API tests passing. Then we'd merge.
I think I understand what the issue is
yeah?
But I'm not sure how to fix it
The image clearly doesn't exist on Docker's page:
docker pull gdcc/base:6.12-noble-p7.2026.2-j21
It wants 2026.7 and only 2026.2 is on Docker
So someone needs to push a 2026.7 image
Can we build the image locally?
I am not sure. The issue is in pom.xml
![]()
I am using the ct container profile to build the container, and the ct profile is using gdcc/base
we can absolutely build it locally and tag it exactly like it expects
Right, but can we build gdcc/base locally, before building the app image.
That's what I do on my laptop to test Payara upgrades: build the base image first. Like this: https://guides.dataverse.org/en/6.11/container/base-image.html#build-instructions
Here too: https://guides.dataverse.org/en/6.11/container/dev-usage.html#building-your-own-base-image
"If you find yourself tasked with upgrading Payara (or reviewing or testing such an upgrade), you will need to create your own base image"
I am building a fix right now
I am testing the workflow fix on Jim's branch now, it seems to be working, but I will keep y'all updated
nice! thanks!
Fix in this PR: https://github.com/IQSS/dataverse/pull/12607
It works on Jim's branch as well, it builds the gdcc/base image locally
Thanks for the PR!
How did you test Jim's branch?
I forked Jim's fork of Dataverse into my personal GitHub account, made commits directly to his branch, opened a PR to dev within it and tested it
https://github.com/srmanda-cs/dataverse/actions/runs/31637279292/job/94250673110
Ok, cool, I figured it was something like that. Thanks.
I guess it will slow down our CI a bit, building the base image. Any idea how much?
2 minutes 30 seconds on average
I'd say it's worth it.
I mean, I guess we could add some logic to only build the base image when Payara is upgraded, right?
We could, yes
it will simply ping Docker to see if an image exists, otherwise it will build it
I am going to go ahead and test that functionality
Sounds great!
Done. Should not have any overhead when the docker image exists now
/me looks at #12607 again
Cool. Once tests are passing I'll merge it. Then ask Jim to update his branch. Thanks again!
When Docker Image doesn't exist
![]()
When docker image exists
![]()
Nice, clear messaging.
Merged! Thanks, @Ash Manda!
Of course! Always happy to help
Last updated: Aug 18 2026 at 08:27 UTC