Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update opentelemetry dependency version to 0.17.1 #18940

Merged
merged 6 commits into from
Feb 23, 2021
Merged

Update opentelemetry dependency version to 0.17.1 #18940

merged 6 commits into from
Feb 23, 2021

Conversation

samvaity
Copy link
Member

@samvaity samvaity commented Feb 2, 2021 •
edited
Loading

Closes #19372

This PR:

@ghost ghost added the Azure.Core azure-core label Feb 2, 2021
@check-enforcer
Copy link

check-enforcer bot commented Feb 2, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@samvaity
Copy link
Member Author

samvaity commented Feb 2, 2021

/azp run java - core - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@samvaity samvaity force-pushed the otel-15-update branch 3 times, most recently from db0aef4 to 3a931c9 Compare February 3, 2021 01:31
@samvaity samvaity changed the title Update opentelemetry 0.15.0 version Update opentelemetry version to 0.15.0 Feb 3, 2021
@samvaity samvaity self-assigned this Feb 3, 2021
@samvaity
Copy link
Member Author

samvaity commented Feb 3, 2021

/azp run java - core - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@samvaity samvaity requested a review from srnagar February 4, 2021 03:03
@samvaity samvaity force-pushed the otel-15-update branch 2 times, most recently from 6a53b63 to e78e391 Compare February 18, 2021 21:23
@samvaity
Copy link
Member Author

/azp run java - core - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@samvaity samvaity force-pushed the otel-15-update branch 4 times, most recently from 8116412 to edb3dd1 Compare February 22, 2021 20:54
@samvaity samvaity changed the title Update opentelemetry version to 0.15.0 Update opentelemetry version to 0.17.1 Feb 22, 2021
@samvaity samvaity changed the title Update opentelemetry version to 0.17.1 Update opentelemetry dependency version to 0.17.1 Feb 22, 2021
@samvaity
Copy link
Member Author

/azp run java - core - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@samvaity samvaity force-pushed the otel-15-update branch 7 times, most recently from 3749fad to 5040e68 Compare February 23, 2021 02:32
@samvaity samvaity marked this pull request as ready for review February 23, 2021 05:51
@joshfree joshfree added this to the [2021] March milestone Feb 23, 2021
@joshfree joshfree added the Client This issue points to a problem in the data-plane of the library. label Feb 23, 2021
@samvaity samvaity merged commit 3d8de45 into Azure:master Feb 23, 2021
@samvaity samvaity mentioned this pull request Mar 3, 2021
Merged
@samvaity samvaity deleted the otel-15-update branch June 22, 2021 20:39
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request May 27, 2022
@wiboris
CodeGen from PR 18940 in Azure/azure-rest-api-specs
fc27467 
Mipatera 2022 06 01 batch management (Azure#18940)

* Baseline commit

* Swagger file and readme

Swapped swaggers

* Examples

* Ran prettier

Prettier

* Added identifiers

minor

Missing identifier

* Prettier

* removing 200 response

* Removed 200 from example

Co-authored-by: wiboris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@trask trask trask left review comments

@srnagar srnagar srnagar approved these changes

@joshfree joshfree joshfree approved these changes

@danieljurek danieljurek Awaiting requested review from danieljurek

@g2vinay g2vinay Awaiting requested review from g2vinay

@JimSuplizio JimSuplizio Awaiting requested review from JimSuplizio

@mitchdenny mitchdenny Awaiting requested review from mitchdenny

@alzimmermsft alzimmermsft Awaiting requested review from alzimmermsft

Assignees

@samvaity samvaity

Labels
Azure.Core azure-core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Milestone
[2021] March
Development

Successfully merging this pull request may close these issues.

[Core Tracing] Upgrade the OTel SDK version to 0.17.1
5 participants
@samvaity @trask @joshfree @alzimmermsft @srnagar