CAMEL-24588: camel-jms - disable IBM MQ tests on GitHub Actions

[Croway]

Claude Code on behalf of Croway

Summary

• JmsComponentIbmMQTest and JmsReplyToIbmMQTest start icr.io/ibm-messaging/mq:10.0.0.0-r3 via Testcontainers. icr.io is not reliably reachable from GitHub Actions runners: when the pull hits the Testcontainers 2-minute limit the class errors with ContainerFetchException, surefire retries it twice, and a single registry hiccup costs ~18 minutes and fails the PR build (see PR #26024, run 33542426658: 292 s + 507 s + 292 s in camel-jms).
• Disable both tests on GitHub Actions only, using the existing @DisabledIfSystemProperty(named = "ci.env.name", matches = "github.com") convention. Jenkins sets ci.env.name=apache.org and keeps running them.
• The incremental build already detects this annotation and warns in the PR comment that the tests need manual verification.

Fixes CAMEL-24588.

Test plan

• mvn test -pl components/camel-jms -Dtest='JmsComponentIbmMQTest,JmsReplyToIbmMQTest' -Dci.env.name=github.com reports both as skipped with the reason
• Without the property the tests are unaffected (still gated by @DisabledOnOs on ARM64)

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• components/camel-jms

---

🔬 Scalpel shadow comparison — Scalpel: 1 tested, 0 compile-only — current: 12 all tested

Maveniverse Scalpel detected 1 affected modules (current approach: 12).

Modules only in current approach (11)

• camel-activemq
• camel-activemq6
• camel-amqp
• camel-jbang-mcp
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher-container
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin

Skip-tests mode would test 1 modules (1 direct + 0 downstream), skip tests for 0 (generated code, meta-modules)

Modules Scalpel would test (1)

• camel-jms

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• components/camel-jms: 3 test(s) disabled on GitHub Actions

All tested modules (12 modules)

• Camel :: AMQP
• Camel :: ActiveMQ 5.x
• Camel :: ActiveMQ 6.x
• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: JMS
• Camel :: Launcher :: Container
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ View full build and test results