jbonofre opened a new pull request, #750: URL: https://github.com/apache/camel-karaf/pull/750
Fixes #748. Backport of #746 to `camel-karaf-4.18.x`. `CamelGooglePubsubITest` on this branch still pins `gcr.io/google.com/cloudsdktool/google-cloud-cli:441.0.0-emulators`. `gcr.io` keeps only a rolling window of the most recent `google-cloud-cli` emulator tags, 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 at `camel-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-emulators` successfully (410 MB in the log). So this had not yet begun failing 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_IMAGE` constant at `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, as in #746. ### Verification CI is the gate here. I could not run `CamelGooglePubsubITest` locally — no Docker 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é._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
