gnodet opened a new pull request, #30263:
URL: https://github.com/apache/camel/pull/30263

   ## Summary
   
   Add 5 missing artifact IDs to `EXCLUSION_LIST` in `incremental-build.sh` so 
they are not spuriously pulled into targeted test runs when unrelated modules 
change.
   
   ## Root Cause
   
   The incremental build script uses `-amd` (also-make-dependents) when 
computing which modules to test after a change. Any module that depends on 
`camel-catalog` (directly or transitively) is pulled into the reactor. Five 
modules were missing from `EXCLUSION_LIST` and were being tested on every 
`camel-catalog`-touching PR:
   
   - `camel-jbang-mcp`
   - `camel-jbang-plugin-validate`
   - `camel-launcher-container`
   - `camel-yaml-dsl-validator`
   - `camel-yaml-dsl-validator-maven-plugin`
   
   ## Fix
   
   Add the five artifact IDs to `EXCLUSION_LIST` on line 51 of 
`.github/actions/incremental-build/incremental-build.sh`, grouped after the 
existing `camel-launcher` entry.
   
   The existing `filterExclusions()` function (line 83) already handles the 
"this module IS the changed module" case: when any of these modules is itself 
the primary changed module, its exclusion entry is automatically lifted, so 
direct changes to these modules are still tested normally.
   
   Note: `camel-jbang-plugin-route-parser` was removed from the codebase 
(CAMEL-25587) and is **not** added.
   
   ## Tests
   
   Validated with a local shell test that exercises `filterExclusions()` for 
all four scenarios:
   1. Each new module as the primary changed module → exclusion lifted ✓
   2. An unrelated module changed → all 5 new entries remain excluded ✓
   3. `camel-jbang-plugin-route-parser` not present in the list ✓
   
   Fixes CAMEL-23326
   
   ---
   _Hermes Agent (Claude Sonnet 4.6) on behalf of Guillaume Nodet_
   


-- 
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]

Reply via email to