ci: test Scalpel shadow comparison — camel-core test-jar change [DO NOT MERGE]#23033
Closed
gnodet wants to merge 4 commits into
Closed
ci: test Scalpel shadow comparison — camel-core test-jar change [DO NOT MERGE]#23033gnodet wants to merge 4 commits into
gnodet wants to merge 4 commits into
Conversation
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Upgrade Scalpel from extension3:0.1.0 to extension:0.3.0 and run it in shadow mode — observing what skip-tests mode would do without affecting actual test execution. This allows validating Scalpel's decisions across many PRs before switching to Scalpel-driven test execution. Changes: - Upgrade Scalpel to 0.3.0 with source-set-aware propagation and skipTestsForDownstreamModules support - Pre-fetch base branch in CI workflow (avoids JGit issues in shallow clones) - Remove persist-credentials: false (needed for git fetch operations) - Add shadow comparison section to PR comments showing what Scalpel skip-tests mode would have tested vs the current approach - Update CI-ARCHITECTURE.md with shadow comparison documentation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Scalpel 0.3.0 upgrade is already on main. This PR focuses on the shadow comparison feature, not the version bump. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Switch the grep-based incremental build script from fetching diffs via the GitHub REST API to using local git merge-base + diff. Both the grep script and Scalpel now share the same --deepen=200 fetch step, removing the GitHub API dependency for diff fetching. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
gnodet
force-pushed
the
test-scalpel-shadow-b
branch
from
6b5cf90 to
53ee2a5
Compare
Contributor
|
🧪 CI tested the following changed modules:
|
Contributor
Author
|
Closing — redesigning with POM changes to trigger Scalpel shadow comparison. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Test PR for Scalpel shadow comparison validation
DO NOT MERGE — this PR exists solely to validate the Scalpel shadow comparison output from PR #22524.
Scenario B: camel-core test-jar change
A trivial comment added to
ContextTestSupport.javain camel-core's test sources (test-jar). Many modules depend on camel-core, but only a subset actually use the test-jar.Expected: The grep-based script should flag all ~500 modules that depend on camel-core. Scalpel's source-set-aware propagation should recognize this is a test-jar-only change and flag far fewer modules — only those that actually depend on the test-jar.
This PR will be closed after validation.