jamesnetherton opened a new pull request, #8790:
URL: https://github.com/apache/camel-quarkus/pull/8790
Adds incremental build support to the CI workflow using Scalpel. Currently
only for PRs.
I have tested it across multiple scenarios on my fork and I think it works
ok.
How it works:
- Scalpel runs during initial-mvn-install and produces a report of affected
modules
- `IncrementalBuildMojo` generates the native test matrix, JVM test list,
and functional test scope flags from the report
- Container image property changes in pom.xml are detected separately
(Scalpel doesn't track these) by scanning *TestResource.java files for
references, including transitive resolution through integration-tests-support/
modules
- Full builds automatically trigger for changes to: poms/build-parent/**,
extensions-core/**, tooling/maven-plugin/**, .mvn/**
- Push events always run full builds; incremental is PR-only
- The full build can be forced by adding the `ci/disable-incremental` label
to a PR.
Future optimisations:
- Move more workflow shell logic into the Maven Mojo
- Explore incremental builds for push events
- Relax full build triggers for extensions-core modules. Likely only needs
to be applied to extensions-core/core
- Start thinking about making parts of our workflows reusable and have the
core parts extracted into composite local actions
--
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]
