-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[IngestionClient] Unit test coverage as part of the CI/CD pipeline #2515
[IngestionClient] Unit test coverage as part of the CI/CD pipeline #2515
Conversation
@HenryvanderVegte this PR is using the GITHUB_TOKEN which will not work on a fork, as you cannot access that Token from a fork. I believe the theory is that this workflow when run under the repo context (not fork) will have access to the token and will be able to write the Test Coverage as a comment in the PR |
/azurepipelines run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azurepipelines run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
@ross-p-smith @HenryvanderVegte @zhouwangzw The azure pipeline build from a forked repo is disabled now for some security reasons, we are contact to ado org admin to see if we can enable it again. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
thanks a lot @yulin-li ! |
Purpose
This PR is actually #2503 but with the comments fixed. Original work has been carried out by @komalg1
This adds Code Coverage report into the project so we can baseline the tests
Pull Request Type
What kind of change does this Pull Request introduce?