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.

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

servicebus core-amqp version upgrade after beta release #20831

Merged

Conversation

hemanttanwar
Copy link
Contributor

We have released beta version of following library from feature branch. Thus increasing the versions.
Following beta libraries are released.

@check-enforcer
Copy link

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

@hemanttanwar hemanttanwar merged commit 22f57af into Azure:master Apr 20, 2021
@hemanttanwar hemanttanwar deleted the servicebus-core-amqp-version-increment branch April 20, 2021 19:07
benbp pushed a commit that referenced this pull request Apr 28, 2021
* servicebus core-amqp version upgrade after beta release

* Added changelog for released beta versions
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request Sep 27, 2022
Add properties to ExpressRoute gateway resource types to allow custom… (Azure#20831)

* Add properties to ExpressRoute gateway resource types to allow customers to control traffic flow

* Fix JSON

* Fix issues.

Co-authored-by: Javier Colomer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core azure-core azure-spring All azure-spring related issues Service Bus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants