Closed SylvainJuge closed 1 week ago
As discussed during June 13th Java SIG meeting, we should start always testing for "indy compatibility" in CI.
This helps for sub-tasks of #11457 that do not require to have the test indy label added to PRs for the test to be effective.
test indy
This also helps to prevent adding new instrumentations that are not "indy compatible" as the ones that were fixed in https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11582
Once this PR is merged then the test indy label could be removed.
merging, if there are any unexpected side-effects we can revisit
As discussed during June 13th Java SIG meeting, we should start always testing for "indy compatibility" in CI.
This helps for sub-tasks of #11457 that do not require to have the
test indy
label added to PRs for the test to be effective.This also helps to prevent adding new instrumentations that are not "indy compatible" as the ones that were fixed in https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11582
Once this PR is merged then the
test indy
label could be removed.