pjfanning opened a new pull request, #1899: URL: https://github.com/apache/pekko-connectors/pull/1899
### Motivation The `ibmmq` docker-compose service (used by both the `jms` and `jakartams` CI jobs) pulls `ibmcom/mq:latest`. The `ibmcom` Docker Hub namespace was abandoned in December 2021 — its `latest` is actually MQ 9.2.4, and IBM has removed `ibmcom` images before, so two active CI jobs sit on a dead, unpinned image. IBM MQ images are now published to the IBM Container Registry as `icr.io/ibm-messaging/mq`. ### Modification - Switch the `ibmmq` service to `icr.io/ibm-messaging/mq:9.4.5.1-r1` (current release, pinned). The existing `LICENSE`/`MQ_QMGR_NAME` environment and 1414/9443 ports are unchanged; on the developer image the `app` user on `DEV.APP.SVRCONN` still connects without a password when `MQ_APP_PASSWORD` is unset, which matches how the tests connect. - Update the docker run command and developer-defaults link in `docs/src/main/paradox/jms/ibm-mq.md` (the old `mq-docker` repo moved to `mq-container`). - Update the image reference comments in the jms/jakartams IBM MQ test files. ### Result The JMS and Jakarta Messaging IBM MQ integration tests run against a current, pinned IBM MQ release from IBM's own registry. ### Tests - `scalafmt --list --mode diff-ref=upstream/main` - clean (comment-only Scala changes). - Not run locally - the `connectors (jms)` and `connectors (jakartams)` CI jobs start this service (`docker compose up -d ibmmq`) and run their suites against it. ### References None - test docker image maintenance -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
