jamesnetherton opened a new pull request, #9283: URL: https://github.com/apache/camel-quarkus/pull/9283
Fixes some issues I opened recently where either the full build was triggered or too many modules were included in the incremental build: https://github.com/maveniverse/scalpel/issues/209 https://github.com/maveniverse/scalpel/issues/213 https://github.com/maveniverse/scalpel/issues/216 Summary of what changed in our workflow and Maven plugin: * Version changes in imported BOMs now only affect the modules using them, instead of triggering a full build * Give the Scalpel analysis step a larger heap (probably need to open a Scalpel issue to investigate high memory consumption) * Run functional tests for affected modules only via -pl, falling back to trim mode for full builds and extensions-core changes * Add a functional test step for extensions-support * Fix catalog scope detection * Detect changed container image properties from the Scalpel report changedProperties instead of grepping the git diff of pom.xml. This also catches properties whose value changes indirectly, such as fhir.container.image via fhir.container.image.base * Remove unused incremental-build mojo actions, leaving the analysis that CI uses as the only behavior -- 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]
