chore: set DO_NOT_TRACK=1 globally in test suite#110
Merged
saurabhjain1592 merged 1 commit intomainfrom Mar 10, 2026
Merged
Conversation
Add DO_NOT_TRACK environment variable to Surefire plugin config, preventing telemetry pings to the checkpoint endpoint during local development and CI test runs.
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
1 participant
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.
Summary
DO_NOT_TRACK=1environment variable to Maven Surefire plugin configurationmvn testruns by any developerContext
Local development was generating ~670 Java SDK telemetry records per session, polluting both DynamoDB and Scarf. CI workflows already set
DO_NOT_TRACK=1, but local test runs did not.Test plan
mvn test -B)