Cyrille Le Clerc

@AndriiChuzhynov can you please test https://github.com/jenkinsci/opentelemetry-plugin/releases/tag/opentelemetry-2.10.0-beta-1 ?

@v1v coudl we clarify a bit the design on https://github.com/jenkinsci/opentelemetry-plugin/issues/173 ? I remember we were wondering if we should introduce OpenTelemetry spêcific attributes at the job level or if we...

Change milestone from v1.0 to later as we don't want to block 1.0 for this standardisation task that will take time aligning with other CI/CD platforms.

Great idea. I'm wondering how we could expose a subset of the OpenTelemetry API directly in the Jenkins pipeline language: * `io.opentelemetry.api.trace.Tracer#spanBuilder()` * `io.opentelemetry.api.trace.SpanBuilder#startSpan()` * `io.opentelemetry.api.trace.Span#current()` * `io.opentelemetry.api.trace.Span#end()`

Thanks @BerndFarkaDyna for your feedback. The value of `ci.pipeline.id` being `path/to/Build/pr-{number}` rather than `path/to/Build/job/PR-123/1` looks definitively like a bug. On the other hand, as @v1v said, we decided to pick...

>About the cardinality on the root span name: Of course I understand you explanation and it makes sense to me, but for me it seems inconsistent since branch-builds of the...

@BerndFarkaDyna can you please explain us how you this naming is impacting you? is it related to the visualization of the list of traces grouped by their "root name"?

I'm convinced by @BerndFarkaDyna 's proposal to use the Pull Request / Change Request pipeline name. IDeally with a configuration entry to specify the naming strategy but we can start...

with pleasure @BerndFarkaDyna , the more contributors we have, the better :-)

> changing the name of the span to the pipeline name. Yes. Question: according to the source code, the change request job name can be suffixed by `-head` or `-merge`....