Update OTel operator variables for one-pipeline 1.5.3 - #12536
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits into
Conversation
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
Please try again by commenting @autotest review.
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What Does This Do
Updates the OpenTelemetry Operator image controls to the
CI_OTEL_OPERATOR_*variable names and updates the locked one-pipeline template from 1.5.1 to 1.5.3.Motivation
DataDog/libdatadog-build#259 prefixed these build-only controls with
CI_so tracer configuration does not interpret them as OpenTelemetry SDK settings. Using one-pipeline 1.5.3 keeps this consumer on the latest published template containing that interface.Additional Notes
CI_OTEL_OPERATOR_IMAGES_ENABLEDandCI_OTEL_OPERATOR_LANGUAGE../gradlew spotlessApplysuccessfully.git diff --checkpasses.Follow-up to #12255. Equivalent consumer update to DataDog/dd-trace-py#20239.
Contributor Checklist
type:,comp:, and AI-generated labels.Jira ticket: N/A