-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup code coverage for OpenSearch repo #2193
Comments
Looks like @peterzhuamazon is working on end to end JenkinsFile for gradle check. |
@gaiksaya : Thanks for providing the update. Can you please elaborate more on task @peterzhuamazon is working upon. I would like to know more how is it related to the ask on this issue. |
Discussed the ask from infra team with @bbarani. Infra team is currently working on public jenkins migration and will help with this issue post existing gradle check migration to public jenkins by end of next week. |
Since we have completed the migration of gradle check in #851 coverage is on the table now. |
PR lists: 20220628: 20220629:
20220706: 20220707: |
The coverage results are published to codecov, tho it is not showing the analysis correctly. Thanks. |
Codecov now shows: |
This task is completed for now close the issue. |
Is your feature request related to a problem? Please describe
Setup code coverage for OpenSearch repo.
Describe the solution you'd like
As part of this issue, we need to
-Dtests.coverage=true
to generate report on CI server. This step generates the report in .xml format underbuild/codeCoverageReport
directory.Documentation on OpenSearch: https://github.com/opensearch-project/OpenSearch/blob/main/TESTING.md#test-coverage-analysis
Issues on OpenSearch:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: