yihua opened a new pull request, #18230:
URL: https://github.com/apache/hudi/pull/18230

   ### Describe the issue this Pull Request addresses
   
   Add Codecov integration to GitHub Actions CI to track code coverage across 
test jobs. Currently, GH Actions runs tests but does not collect or report 
coverage data to Codecov. Azure CI has coverage via JaCoCo, but the GH Actions 
workflow lacks equivalent reporting. Eventually, we will migrate all jobs from 
Azure CI to GH Actions so coverage report from GH Actions is needed.
   
   ### Summary and Changelog
   
   Enable cross-module JaCoCo coverage reporting in GitHub Actions and upload 
merged reports to Codecov.
   
   Changes:
   - Enable JaCoCo (`-Djacoco.skip=false`) on 9 existing test jobs 
(`test-spark-java-tests-part1/2/3`,
     `test-spark-scala-dml-tests`, `test-spark-scala-other-tests`, 
`test-hudi-hadoop-mr-and-hudi-java-client`, `test-flink-1`, `test-flink-2`);
   - After each coverage-enabled job, generate a merged cross-module JaCoCo XML 
report and upload to Codecov via `codecov/codecov-action@v5`;
   - Update `.codecov.yml` comment behavior to new (post new comment per push 
instead of editing).
   
   Key design decisions:
   - Merged reports capture cross-module coverage (e.g., tests in 
hudi-spark-client exercising code in hudi-client-common).
   - Codecov server side merges coverage from all job uploads so no cross-job 
aggregation is needed.
   
   ### Impact
   
   Code coverage report change only
   
   ### Risk Level
   
   none
   
   ### Documentation Update
   
   none for now.  Once all CI changes are done and stable, we'll update the 
developer guide.
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


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