aldettinger commented on PR #8790:
URL: https://github.com/apache/camel-quarkus/pull/8790#issuecomment-4787984263
Hard to review indeed, still really worth it. It's better optimization than
removing duplicate tests from camel and speeding up the full build by any
optimization. The incremental build could actually compound with those if ever
needed.
Here are the current understanding of a few scenarios for double checking:
+ Update quarkus version (probably near full build as scalpel would include
a lot)
+ An `extensions-support` modified (scalpel should include only what's
needed base on dependencies)
+ Changing .github files (An empty build will be triggered)
+ Test groups are rebalanced (An empty build will be triggered)
+ Changing an application.properties file (scalpel should include needed
dependencies)
What do you think ?
--
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]
