Code coverage

[mloufra]

Description

The purpose for this PR is to use JaCoCo to collect these results and push them to codecov.io.
The following step is my idea to hit the mark.

• Add JaCoCo Gradle plugin to generate code coverage report for opensearch-sdk-java
• Upload code coverage report to codecov.io through build workflow (Not sure we need to create another yml file to handle that, so I pick the most relevant build.yml to add the code after reviewing each yml file in workflow folder)
• Add status badge to show the code coverage
• Add covdecov integration in pull request

Issues Resolved

#48

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.

[saratvemulapalli]

@mloufra if it's ready for review can you flip the PR from draft?

Also the suggestion from @dbwiddis makes a lot sense. Can we use auto so that the threshold always goes up.

[mloufra]

@mloufra if it's ready for review can you flip the PR from draft?

Also the suggestion from @dbwiddis makes a lot sense. Can we use auto so that the threshold always goes up.

After I make change on target percent to atuo, I will flip the PR from draft

[owaiskazi19]

@mloufra can you link an example of the codecov report being published as a PR Comment?

[mloufra]

@mloufra can you link an example of the codecov report being published as a PR Comment?

I will try to make one today

[owaiskazi19]

Failure in build:

FAILURE: Build failed with an exception.

* What went wrong:
Problem configuring task :check from command line.
> Unknown command-line option '--coverage'.

[mloufra]

Failure in build:

FAILURE: Build failed with an exception.

* What went wrong:
Problem configuring task :check from command line.
> Unknown command-line option '--coverage'.

The unknown command-line option --coverage has been deleted. This Failure will not happen any more.

[owaiskazi19]

Approving it to see if codecov will work once codecov.yml is in. We can always revert this change if it doesn’t :)

[mloufra]

Approving it to see if codecov will work once codecov.yml is in. We can always revert this change if it doesn’t :)

I agree with this idea. Let me explain little more about what's going on. For now, We are able to generate the code coverage report for our branch, and push the report to Codecov.io. (Through this Link we can see the report has been pushed successfully). The problem is that Codecov.io does not show up our code coverage report on its page. It keeps showing "No data available", it means the repo is not setup successfully. In general step, we should ask for organization access to setup repo. After I doing research and contact with Tianli, opensearch-project organization has denied this requirement before and most team who succeed to setup repo also do not have this access. And I check the Guideline for code coverage, it has no description of this situation. So I think we can try to approve it to see what happen.

[owaiskazi19]

It worked on README. @mloufra The next step is to monitor if codecov is commenting the report on the PRs.

[dbwiddis]

I like our report and the badge that gets us quickly to it! Will really help us audit our code coverage.

[mloufra]

The Codecov comment is running successfully. Here is the link.

[dbwiddis]

The Codecov comment is running successfully. Here is the link.

Glad it was my awesome well-covered PR that proves it's working. 😀