-
Notifications
You must be signed in to change notification settings - Fork 138
Move code coverage from GitHub Actions to Azure Pipeline #2433
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
base: dev
Are you sure you want to change the base?
Conversation
Co-authored-by: fadidurah <[email protected]>
Co-authored-by: fadidurah <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request confirms that the code-coverage workflow already supports label-triggered reruns without requiring additional implementation. The PR clarifies that the existing workflow configuration includes both labeled and unlabeled event types in the pull_request trigger, enabling automatic re-execution when the code-coverage-skip label is added or removed.
Changes:
- Added comprehensive GitHub Actions workflow for code coverage checking on PRs targeting the
devbranch - Implemented dual-job pattern with separate jobs for running coverage checks and handling skip scenarios
- Integrated Jacoco-based coverage comparison between PR branch and dev branch with clear pass/fail criteria
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
📊 Code Coverage Report❓ UNKNOWN
This check can be skipped by adding the |
✅ Code Coverage Report✅ PASSED
Code coverage maintained at 0.0%. This check can be skipped by adding the |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: fadidurah <[email protected]>
✅ Code Coverage Report✅ PASSED
Code coverage maintained at 0.0%. This check can be skipped by adding the |
- Ensure gradle.properties ends with newline before appending - Check for existing properties to avoid duplicates - Add better logging for gradle.properties setup This fixes the error: 'Provider com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImplvstsUsername=dummy not found' which occurred when appending properties without proper newline separation.
✅ Code Coverage Report✅ PASSED
Code coverage maintained at 0.0%. This check can be skipped by adding the |
- Add code coverage generation to pr-msal.yml Azure Pipeline - Disable GitHub Actions code-coverage.yml workflow - Add documentation explaining the change The GitHub Actions workflow cannot access internal Azure DevOps artifact feeds required for running MSAL tests. The Azure Pipeline already runs tests with proper authentication, so we add coverage generation there instead. Co-authored-by: fadidurah <[email protected]>
GitHub Actions cannot authenticate to internal Azure DevOps artifact feeds required for MSAL test execution. The existing
pr-msal.ymlpipeline (definitionId=1328) already runs tests with proper authentication on every PR.Changes
azure-pipelines/pull-request-validation/pr-msal.ymlPublishCodeCoverageResults@1task to publish coverage to Azure DevOps.github/workflows/code-coverage.yml.code-coverage.yml.disabled).github/workflows/CODE_COVERAGE_README.mdCoverage Location
Coverage reports are available in Azure DevOps pipeline runs under the "Code Coverage" tab.
Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.