-
Notifications
You must be signed in to change notification settings - Fork 134
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
Change to release after SDK and before Instrumentation #1581
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,15 +7,13 @@ data class DependencySet(val group: String, val version: String, val modules: Li | |
val dependencyVersions = hashMapOf<String, String>() | ||
rootProject.extra["versions"] = dependencyVersions | ||
|
||
val otelInstrumentationVersion = "2.10.0-alpha" | ||
|
||
val DEPENDENCY_BOMS = listOf( | ||
"com.fasterxml.jackson:jackson-bom:2.18.2", | ||
"com.google.guava:guava-bom:33.3.1-jre", | ||
"com.linecorp.armeria:armeria-bom:1.31.2", | ||
"org.junit:junit-bom:5.11.3", | ||
"io.grpc:grpc-bom:1.68.2", | ||
"io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:${otelInstrumentationVersion}", | ||
"io.opentelemetry:opentelemetry-bom-alpha:1.44.1-alpha", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't update to 1.45.0 in order to ensure everything works smoothly when renovate updates it after this PR is merged |
||
"org.testcontainers:testcontainers-bom:1.20.4" | ||
) | ||
|
||
|
@@ -78,12 +76,6 @@ javaPlatform { | |
|
||
dependencies { | ||
for (bom in DEPENDENCY_BOMS) { | ||
// this is needed until io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha | ||
// is updated to contain the latest version of opentelemetry-semconv | ||
if (bom.equals("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:${otelInstrumentationVersion}")) { | ||
api(platform(bom)) | ||
continue | ||
} | ||
api(enforcedPlatform(bom)) | ||
val split = bom.split(':') | ||
dependencyVersions[split[0]] = split[2] | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,7 +22,7 @@ dependencies { | |
runtimeOnly("io.opentelemetry:opentelemetry-exporter-otlp") | ||
runtimeOnly("io.opentelemetry:opentelemetry-exporter-logging") | ||
|
||
implementation("io.opentelemetry.instrumentation:opentelemetry-jmx-metrics") | ||
implementation("io.opentelemetry.instrumentation:opentelemetry-jmx-metrics:2.10.0-alpha") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Moving contrib before instrumentation in the release allows to remove this circular dependency if we move the JMX insights code directly into contrib and then reuse it as-is in instrumentation. Do you think this would be something relevant to do ? It also changes a bit the "ownership" of the JMX-related code in the instrumentation by relying on the component owners of contrib instead. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think I'd prefer to go in the other direction and keep / move things that we release as part of the core java agent distribution into the java instrumentation repo (@laurit wdyt? EDIT: we could introduce "component owners" in that repo similar to this repo) @jackshirazi would this address your concern about release ordering, and we could go back to releasing instrumentation repo first and then contrib repo? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I understand that means:
One interesting aspect of adding component owners directly in instrumentation is that it helps to delegate changes that are related to those components to their respective owners. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The concern is that if any contrib project needs a fix, it's an extra month before the agent gets that fix (if we release agent before contrib). It's not a dramatically bad concern, and it hasn't been an actual issue so far. |
||
|
||
testImplementation("org.junit-pioneer:junit-pioneer") | ||
testImplementation("io.opentelemetry:opentelemetry-sdk-testing") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking to change the Instrumentation release date to the Thursday after this