Repository navigation
fix(#748): bump the Pub/Sub emulator image on 4.18.x to a tag gcr.io still serves - #750
Merged
jbonofre merged 1 commit intoSep 6, 2026
Conversation
…cr.io still serves Backport of apache#746. CamelGooglePubsubITest on this branch still pins gcr.io/google.com/cloudsdktool/google-cloud-cli:441.0.0-emulators. That tag still resolved on 2026-08-28 -- the CI run for PR apache#742 pulled it successfully -- but gcr.io keeps only a rolling window of the most recent emulator tags, so the pin has since stopped resolving. The failure mode is the one apache#746 described on main: Testcontainers fails the container fetch with "manifest unknown", the itest errors out in initializationError, and the reactor halts at camel-google-pubsub-test, skipping every later module. That blocks meaningful CI on the 4.18.x line, including PR apache#742. Bump it to 583.0.0-emulators and keep the comment recording the registry retention behaviour, so the next bump is not a mystery. The other four pinned test images (cp-kafka, influxdb, localstack, rabbitmq) are untouched.
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
1 participant
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.
Fixes #748. Backport of #746 to
camel-karaf-4.18.x.CamelGooglePubsubITeston this branch still pinsgcr.io/google.com/cloudsdktool/google-cloud-cli:441.0.0-emulators.gcr.iokeeps only a rolling window of the most recent
google-cloud-cliemulatortags, so that pin has stopped resolving.
Testcontainers then fails the container fetch with "manifest unknown", the
itest errors out in
initializationError, and the Maven reactor halts atcamel-google-pubsub-test, skipping every later module — the same failure#746 fixed on
main.This is currently blocking meaningful CI on the 4.18.x line, including
PR #742 (Upgrade to Camel 4.18.4), whose CI cannot be re-run and trusted until
this lands.
Timing note
The tag was still being served recently: PR #742's CI run on 2026-08-28 pulled
441.0.0-emulatorssuccessfully (410 MB in the log). So this had not yet begunfailing on 4.18.x at that point — it is failing now.
Change
The commit is a verbatim cherry-pick of #746's single-file change: extract the
image into a
PUB_SUB_EMULATOR_IMAGEconstant at583.0.0-emulators, and keepthe comment recording the registry retention behaviour so the next bump is not
a mystery.
The other four pinned test images (cp-kafka, influxdb, localstack, rabbitmq)
are untouched, as in #746.
Verification
CI is the gate here. I could not run
CamelGooglePubsubITestlocally — noDocker daemon available in my environment — so the Testcontainers path is
unverified on my side. The change is identical to the one already green on
main.Opened by an AI agent operated by JB Onofré.