Skip to content

Add Datadog code coverage upload#43

Draft
ManuelPalenzuelaDD wants to merge 5 commits intoDataDog:mainfrom
ManuelPalenzuelaDD:add-datadog-coverage
Draft

Add Datadog code coverage upload#43
ManuelPalenzuelaDD wants to merge 5 commits intoDataDog:mainfrom
ManuelPalenzuelaDD:add-datadog-coverage

Conversation

@ManuelPalenzuelaDD
Copy link
Copy Markdown
Collaborator

@ManuelPalenzuelaDD ManuelPalenzuelaDD commented Mar 12, 2026

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

  • Added DataDog/coverage-upload-github-action@v1 step after the existing Codecov upload in the dev.yml workflow test job
  • Uses DD_API_KEY_CI_APP secret (already available in the repo for CI Visibility)
  • Coverage format: LCOV (generated by llvm-cov export)
  • The existing Codecov uploads are unchanged — nothing is removed or modified
  • The upload uses continue-on-error: true so it cannot block CI

Why 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:

  • Coverage data integrated directly into Datadog CI Visibility
  • PR gates and coverage checks natively in Datadog
  • No dependency on a third-party service (Codecov) for coverage reporting

Validation

Pending — dev.yml triggers on push only (not PRs), so the Datadog upload will run after merge.

Next steps (not in this PR)

Once this PR is merged and we've confirmed Datadog coverage is stable over several commits:

  1. Remove the Codecov upload steps and CODECOV_TOKEN secret
  2. Optionally configure PR gates in code-coverage.datadog.yml

No 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.

ManuelPalenzuelaDD and others added 5 commits March 12, 2026 15:08
Adds DataDog/coverage-upload-github-action step after the existing
Codecov upload in the dev workflow test job. Both systems run in
parallel to verify coverage parity before migrating off Codecov.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Pin DataDog/coverage-upload-github-action@v1 to commit SHA
d2cf302a39c05e0ad22063360a2bf6ce0cc4906c for supply chain security.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The DataDog/coverage-upload-github-action uses install-datadog-ci-github-action
internally, which resolves script paths using github.action_path. In Docker
container jobs, this host path is not accessible inside the container, causing
"No such file or directory" errors.

Using the CLI directly via curl avoids this issue.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@datadog-official
Copy link
Copy Markdown

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 52.72%

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 8351ce5 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant