Exercise the bktec OTLP relay in the RSpec example

[pda]

The RSpec example should exercise the same OTLP-only path customers can use with bktec, rather than sending execution spans directly from the test process to Buildkite.

Changes

• pin the RSpec job to tests#v1.0.1 and bktec v3.1.0-rc.1, which contains the experimental relay
• use the released Ruby collector 2.15.0, including its documented optional OpenTelemetry SDK and OTLP exporter dependencies
• enable BUILDKITE_TESTS_OTLP_RELAY for the RSpec pipeline step
• rely on bktec's standard OTEL_EXPORTER_OTLP_TRACES_* environment instead of configuring a relay-specific token in spec_helper.rb
• keep legacy result upload disabled so the example demonstrates trace-only submission

Context

• Includes the relay from buildkite/test-engine-client#624
• Related to TE-6777

Testing

• parsed .buildkite/pipeline.yml
• bundle check
• loaded Ruby collector 2.15.0 with OpenTelemetry SDK 1.13.0
• ran spec/models/user_spec.rb against a local fake OTLP endpoint; two requests arrived with the standard Bearer header overriding a different collector token, plus the buildkite.otlp.endpoint resource attribute

Rollback

Remove BUILDKITE_TESTS_OTLP_RELAY, the client pin, and the released collector dependency changes.

[buildsworth-bk-app]

Because this switches the example onto a per-run relay credential, it sits above this repository's AI approval ceiling. I didn't find an implementation issue in the change.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 20304, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

About buildsworth

Model: gpt-5.6-sol with xhigh thinking.

How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.

Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):

• L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
• L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
• L3 — High risk (auth, migrations, payments, secrets, perf-critical paths). Human review always required.

[buildsworth-bk-app]

This still routes the RSpec example through bktec's per-run local relay credential, so the runtime and authentication change remains above this repository's AI approval ceiling. I didn't find an implementation issue in the current revision.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 20844, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

[pda]

@buildsworth-bk review approve L2

[pda]

I'll leave this as draft for now, until we have proper bktec and test-collector-ruby releases to use.

[pda]

Rebased against the latest origin/main (the branch was already current, so no history rewrite was needed) and pushed 70cab23.

This now uses the released buildkite-test_collector 2.15.0 with its documented optional OpenTelemetry dependencies, while retaining bktec v3.1.0-rc.1.

Verification:

• bundle check
• pipeline YAML parse
• local fake OTLP endpoint received two trace requests with the relay Bearer header and buildkite.otlp.endpoint resource attribute

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	gem/​buildkite-test_collector@​2.15.0

View full report