Hi everyone,
My name is Seniru and I am a Computer Science student and a Software Engineer. I’m writing to introduce myself and express my strong interest in contributing to the “Use OpenTelemetry for Jenkins Jobs on ci.jenkins. io” project for GSoC 2026.
I have spent the last three and a half years working heavily with Jenkins as the primary CI/CD automation server in a professional enterprise environment. Managing everyday pipelines has given me a solid understanding of the platform’s architecture and I am highly interested in the observability and DevOps domain.
To prepare for this project, I have started building a local Proof of Concept (PoC) by spinning up a Jenkins instance, hooking it up to an OpenTelemetry Collector and routing the telemetry data to a local Jaeger backend. I am currently experimenting with how the trace context propagates through nested pipeline stages.
As I look deeper into the scale of ci.jenkins.io, I had a quick question for the mentors and infrastructure team: When configuring the OTel Collector for the project, is the primary goal to rely on tail-based sampling to manage high cardinality and storage costs for successful builds or is the focus more on ensuring the telemetry routing is entirely backend-agnostic for the community?
I am currently looking through the issue tracker to find a good first issue to work on. I look forward to learning from this community and collaborating with you all!
Best regards,
Seniru
https://www.linkedin.com/in/senirus/