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

   ## Summary
   
   _Claude Code on behalf of gnodet_
   
   When using `gh run rerun --failed`, the **Fetch base branch for Scalpel 
change detection** step does not re-execute (it succeeded in the original run 
and is skipped on re-run), leaving git state incomplete. Scalpel (configured in 
`.mvn/extensions.xml`) then fails when loaded during the **Get Atlassian 
dependency version** step, causing `help:evaluate` to exit with code 1.
   
   Since `help:evaluate` only reads a property value from the POM and does not 
need Scalpel's change detection, this PR disables Scalpel with 
`-Dscalpel.enabled=false` for that step.
   
   ### Changes
   
   - `.github/workflows/pr-build-main.yml`: Add `-Dscalpel.enabled=false` to 
`help:evaluate` invocation
   - `.github/workflows/main-build.yml`: Add `-Dscalpel.enabled=false` to 
`help:evaluate` invocation
   
   ### Root cause
   
   Failed run: https://github.com/apache/camel/actions/runs/32765151716
   
   The `build (25, false)` job failed because:
   1. The Scalpel Maven extension loads for all `./mvnw` invocations (via 
`.mvn/extensions.xml`)
   2. Scalpel needs git merge-base state set up by the "Fetch base branch" step
   3. On `gh run rerun --failed`, previously-succeeded steps are skipped, so 
the git state is never prepared
   4. Scalpel fails to initialize → `help:evaluate` exits with code 1 → empty 
Atlassian version → broken cache key
   
   ## Test plan
   
   - [x] Verify the change is minimal and only affects the `help:evaluate` step
   - [ ] Verify CI passes on this PR (the `help:evaluate` step should succeed 
with Scalpel disabled)
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


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