[HUDI-7596] Enable Jacoco code coverage report across multiple modules

[danny0405]

Change Logs

Enable the Jacoco code coverage for Azure CI.

Impact

none

Risk level (write none, low medium or high below)

none

Documentation Update

none

Contributor's checklist

• [ ] Read through contributor's guide
• [ ] Change Logs and Impact were stated clearly
• [ ] Adequate tests were added if applicable
• [ ] CI passed

[danny0405]

@hudi-bot run azure

[hudi-bot]

CI report:

• 39c44a33eaae3bc17270cec93536ce727daacd98 UNKNOWN
• d329d241fef55c438e72343e4564671df92befff UNKNOWN
• 7d82c286ff67aa8a745651bf23cdb25b161b7919 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[vinothchandar]

I notice that the azure CI results are now grouped by folders? and could we show an example to illustrate that cross module FT coverage is now factored in?

Could we fix these before landing?

[danny0405]

I notice that the azure CI results are now grouped by folders? and could we show an example to illustrate that cross module FT coverage is now factored in?

Could we fix these before landing?

In order to make the cross module FT coverage work, we need to:

1. add a new separate module that including dependencies of all the modules that we want to report;
2. run all the module tests in one shot and there is no way to run specific module with -pl option;

Our CI tests are split into 6 jobs with each covering different modules, which is not suitable for the jacoco report-aggregate goal.

[yihua]

Closing this PR for now since Jacoco coverage report does not fit into our CI job running model.