You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Validate the v1 trace intake protocol in system-tests before it becomes the Java tracer default. The coverage should exercise the shared DEFAULT suite across Java weblogs and a representative complete weblog matrix without introducing a tracer-agnostic scenario.
Changes
Duplicate Java prod jobs containing DEFAULT, keep only the DEFAULT scenario in those copies, and suffix their job instance with _v1.
Duplicate all three spring-boot-jetty CI shards (1_v1, 2_v1, and 3_v1) with their complete scenario lists.
Pass per-job weblog environment overrides through the reusable end-to-end workflow.
Force DD_TRACE_AGENT_PROTOCOL_VERSION=1.0 in the duplicated jobs.
Remove the dedicated DEFAULT_V1 scenario and its special test-selection/framework handling.
Remove the obsolete DD_APM_ENABLE_V1_TRACE_ENDPOINT setting from APM_TRACING_EFFICIENT_PAYLOAD; current Agents expose the v1 endpoint by default.
Impact
The additional coverage is restricted to Java prod jobs. Java dev and all other tracers keep their existing matrices unchanged.
YAML formatting, yamllint, and workflow parser checks passed.
The repository-wide formatter reaches an unrelated existing failure in utils/scripts/shellcheck.sh:74 (@: unbound variable) after the relevant checks pass.
Workflow
⚠️ Create your PR as draft ⚠️
Work on your PR until the CI passes.
Mark it as ready for review:
Test logic is modified → get a review from the RFC owner.
Framework is modified, or usage is non-obvious → get a review from the R&P team.
🚀 Once the PR is reviewed and CI is green, it can be merged.
AlexeyKuznetsov-DD
changed the title
Add DEFAULT_V1 scenario for Java and Go
Add DEFAULT_V1 scenario for tracers that support v1 protocol, but not yet use it by default
Aug 3, 2026
AlexeyKuznetsov-DD
changed the title
Add DEFAULT_V1 scenario for tracers that support v1 protocol, but not yet use it by default
Add scenarios duplicates for dd-trace-java with forced v1 protocol.
Aug 5, 2026
AlexeyKuznetsov-DD
changed the title
Add scenarios duplicates for dd-trace-java with forced v1 protocol.
Add scenario duplicates for dd-trace-java with forced v1 protocol
Aug 5, 2026
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
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.
Motivation
Validate the v1 trace intake protocol in system-tests before it becomes the Java tracer default. The coverage should exercise the shared DEFAULT suite across Java weblogs and a representative complete weblog matrix without introducing a tracer-agnostic scenario.
Changes
DEFAULT, keep only theDEFAULTscenario in those copies, and suffix their job instance with_v1.spring-boot-jettyCI shards (1_v1,2_v1, and3_v1) with their complete scenario lists.DD_TRACE_AGENT_PROTOCOL_VERSION=1.0in the duplicated jobs.DEFAULT_V1scenario and its special test-selection/framework handling.DD_APM_ENABLE_V1_TRACE_ENDPOINTsetting fromAPM_TRACING_EFFICIENT_PAYLOAD; current Agents expose the v1 endpoint by default.Impact
The additional coverage is restricted to Java prod jobs. Java dev and all other tracers keep their existing matrices unchanged.
Validation
./run.sh TEST_THE_TEST tests/test_the_test/test_ci_orchestrator.py tests/test_the_test/test_docker_scenario.py::test_load_environment_overrides tests/test_the_test/test_build_pipeline.py tests/test_the_test/test_gitlab_pipeline_structure.py— 23 passed.utils/scripts/shellcheck.sh:74(@: unbound variable) after the relevant checks pass.Workflow
🚀 Once the PR is reviewed and CI is green, it can be merged.
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified: approval from the R&P team.build-XXX-imagelabel is present.