Add Datadog code coverage upload#2750
Closed
ManuelPalenzuelaDD wants to merge 2 commits into
Closed
Conversation
Side-by-side coverage reporting: adds Datadog coverage upload alongside existing Codecov upload using DataDog/coverage-upload-github-action. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Pin DataDog/coverage-upload-github-action@v1 to commit SHA d2cf302a39c05e0ad22063360a2bf6ce0cc4906c for supply chain security. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2750 +/- ##
==========================================
- Coverage 38.80% 38.42% -0.38%
==========================================
Files 309 309
Lines 26750 27307 +557
==========================================
+ Hits 10379 10494 +115
- Misses 15592 16035 +443
+ Partials 779 778 -1
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Collaborator
|
Closing in favor of #2773 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
We're migrating Datadog repositories from Codecov to Datadog Code Coverage for tracking test coverage. This PR is the first step: it adds a Datadog coverage upload alongside the existing Codecov upload so we can run both systems in parallel and verify parity before switching over.
Changes
DataDog/coverage-upload-github-action@v1step to thebuildjob inmain.yml, running after the existing Codecov uploadcover.outandcover_integration.outwith theunittestsflag (mirroring Codecov)if: always()andcontinue-on-error: trueso it cannot block CIWhy are we doing this?
As part of a company-wide effort, we're consolidating code coverage reporting into Datadog's own Code Coverage product. This gives us:
Validation
Pending — the Datadog upload requires
DD_API_KEYwhich is not available to fork PRs. Coverage comparison will be possible after merge or when CI runs from the base repo.Next steps (not in this PR)
Once this PR is merged and we've confirmed Datadog coverage is stable over several commits:
CODECOV_TOKENsecretcode-coverage.datadog.ymlNo action needed from reviewers beyond normal review
This is a low-risk, additive change. The new upload step runs independently of the existing CI pipeline and cannot cause test failures.