-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combine spans from Gradle into a parent Jenkins trace #1
Comments
Hi @jacob-bresciani-everbridge I wrote this as a proof of concept. Feel free to do with it as you please. :) |
I'm guessing you'd want to figure out some way to propagate the trace from whatever jenkins is doing, and pick it up using a propagator at the beginning of the process, but I'm not familiar with how the jenkins plugin works, so you'd have to figure that bit out, I think. |
Just FYI, this code is super out of date with the OpenTelemetry libraries; I have no idea if it even works any more. :) |
ha, good to know, it still works with the current collector just fine btw. |
I'd be very happy if someone wanted to take ownership of this and contribute to the opentelemetry-java-contrib repo... I don't have the bandwidth to manage it, though. |
I'm looking at using this plugin but having the gradle build triggered from a Jenkins job which is using the Jenkins opentelemetry plugin. Unfortunately this results in a trace for the Jenkins job and a separate trace for the gradle task. Is it possible to have the gradle spans show up in Jenkins job's trace?
The text was updated successfully, but these errors were encountered: