Skip to content

Conversation

Divyaasm
Copy link
Contributor

Description

  1. Triggers parallel jenkins jobs for server module and rest.
    2.Fetches and updates the jobs status
  2. Supports code coverage report generation for unit tests and integration with distinct flags.
  3. Generalizes status comments on PR.

Related Issues

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Divya Madala <[email protected]>
@Divyaasm Divyaasm requested review from a team, jed326 and peternied as code owners October 14, 2025 18:05
@Divyaasm Divyaasm changed the title Update gradle check yaml file to support server module split Support server module split in the gradle-check gh action Oct 14, 2025
@github-actions
Copy link
Contributor

✅ Gradle check result for de55833: SUCCESS

@codecov
Copy link

codecov bot commented Oct 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.14%. Comparing base (252cff8) to head (de55833).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19633      +/-   ##
============================================
+ Coverage     73.11%   73.14%   +0.03%     
- Complexity    70661    70746      +85     
============================================
  Files          5724     5725       +1     
  Lines        323498   323737     +239     
  Branches      46852    46881      +29     
============================================
+ Hits         236518   236790     +272     
- Misses        67846    67926      +80     
+ Partials      19134    19021     -113     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@peterzhuamazon
Copy link
Member

Hi @Divyaasm that means each commit now trigger 2 gradle checks.

With out previous discussion can you open another PR in build repo to increase the amount of runs assigned to gradle check workflow?

Thanks.

@peterzhuamazon
Copy link
Member

And I think this would worth a changelog.md entry because it has a big effect on the PRs going forward.

Thanks.

@Divyaasm
Copy link
Contributor Author

Hi @Divyaasm that means each commit now trigger 2 gradle checks.

With out previous discussion can you open another PR in build repo to increase the amount of runs assigned to gradle check workflow?

Thanks.

Sure Peter let me increase the executors count on the open PR in build repo.

target: 70% # the required coverage value
threshold: 1% # the leniency in hitting the target
unit-tests:
target: 60%
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curious how did we come up with these nums? What are we at today with this broken out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants