Skip to content

Push code coverage data to 1es telemetry#5368

Merged
rbans96 merged 2 commits intomainfrom
personal/ribans/push-code-coverage-to-1estelemetry
Feb 5, 2026
Merged

Push code coverage data to 1es telemetry#5368
rbans96 merged 2 commits intomainfrom
personal/ribans/push-code-coverage-to-1estelemetry

Conversation

@rbans96
Copy link
Contributor

@rbans96 rbans96 commented Feb 3, 2026

Description

Push code coverage data to 1es telemetry.

Related issues

Addresses 182694

Testing

Verified for fhir-service repo, code coverage data is pushed in 1es telemetry for this PR run.
CodeCoverageModule
| where EtlProcessDate > ago(1d)
| where OrganizationName == "microsofthealthoss"

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@rbans96 rbans96 added this to the CY25Q3/2Wk07 milestone Feb 3, 2026
@rbans96 rbans96 requested a review from a team as a code owner February 3, 2026 23:21
@rbans96 rbans96 added Build Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs No-PaaS-breaking-change labels Feb 3, 2026
@rbans96 rbans96 marked this pull request as draft February 3, 2026 23:22
@rbans96 rbans96 added the No-ADR ADR not needed label Feb 4, 2026
@rbans96 rbans96 marked this pull request as ready for review February 4, 2026 17:30
LTA-Thinking
LTA-Thinking previously approved these changes Feb 4, 2026
@rbans96 rbans96 enabled auto-merge (squash) February 4, 2026 17:38
rajithaalurims
rajithaalurims previously approved these changes Feb 4, 2026
Remove PublishCodeCoverageResults@2 from individual test jobs (SQL and Cosmos).
Coverage is now only published once from aggregate-coverage.yml, which:
- Fixes Summary vs Code Coverage tab discrepancy on manual stage retry
- Still collects coverage artifacts from all test jobs
- Aggregates and publishes combined coverage to Azure DevOps UI and 1ES telemetry
@rbans96 rbans96 dismissed stale reviews from rajithaalurims and LTA-Thinking via dd18261 February 4, 2026 19:54
@rbans96
Copy link
Contributor Author

rbans96 commented Feb 4, 2026

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rbans96 rbans96 merged commit 5c3bed3 into main Feb 5, 2026
61 checks passed
@rbans96 rbans96 deleted the personal/ribans/push-code-coverage-to-1estelemetry branch February 5, 2026 03:49
mikaelweave pushed a commit that referenced this pull request Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Build No-ADR ADR not needed No-PaaS-breaking-change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants