You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "Croway (via GitHub)" <gi...@apache.org> on 2026/10/14 11:22:10 UTC

[PR] [backport camel-4.22.x] ci: apply threshold to Scalpel-detected modules in incremental build [camel]

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

   Backport of #26025 (`d32f9bf44407`, straight cherry-pick, no conflicts) to `camel-4.22.x`.
   
   ## Why
   
   On `camel-4.22.x`, Scalpel runs on every PR and its `affectedModules` are merged into the `-pl` build list, but the 50-module threshold only disables `-amd`. It does not drop the modules Scalpel already listed. So any 4.22.x PR touching a core module (e.g. `core/camel-util`) tests ~590 modules.
   
   This is happening now: #27804 and #27781 (both touch `core/camel-util`) have been in `mvn test` for ~1.5h. The same lra change took ~15 min on `main` (#27719) and ~20 min on 4.18.x. Each of these runs holds two runners while the queue is already ~2h deep.
   
   ## Change
   
   When the threshold is exceeded, clear the grep and Scalpel dependency-detected modules from the build list. Only the directly changed modules are tested, as before Scalpel. The `test-dependents` label still forces testing all dependents.
   
   ## Not backported
   
   `a1ebe9f8db73` (#26705) only changes how the Scalpel shadow comparison is shown in the PR comment, so it does not affect which modules get built or tested. I left it out.
   
   _Claude Code on behalf of Croway_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [backport camel-4.22.x] ci: apply threshold to Scalpel-detected modules in incremental build [camel]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #27829:
URL: https://github.com/apache/camel/pull/27829#issuecomment-6168602587

   :star2: Thank you for your contribution to the Apache Camel project! :star2:
     :robot: CI automation will test this PR automatically.
   
     :camel: 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](https://camel.apache.org/community/team/#committers) have access to the summary.
     
     :warning: Be careful when sharing logs. Review their contents before sharing them publicly.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [backport camel-4.22.x] ci: apply threshold to Scalpel-detected modules in incremental build [camel]

Posted by "Croway (via GitHub)" <gi...@apache.org>.
Croway merged PR #27829:
URL: https://github.com/apache/camel/pull/27829


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org