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

[AutoRelease] t2-sqlvirtualmachine-2022-03-02-66648 #23273

Merged
merged 1 commit into from
Mar 4, 2022
Merged

[AutoRelease] t2-sqlvirtualmachine-2022-03-02-66648 #23273

merged 1 commit into from
Mar 4, 2022

Conversation

azclibot
Copy link
Contributor

@azclibot azclibot commented Mar 2, 2022

https://github.com/Azure/sdk-release-request/issues/2465
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1034
BuildTargetingString
azure-mgmt-sqlvirtualmachine
Skip.CreateApiReview
true

@azure-sdk
Copy link
Collaborator

issue link:https://github.com/Azure/sdk-release-request/issues/2465

@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Mar 2, 2022
@ghost
Copy link

ghost commented Mar 2, 2022

Thank you for your contribution azclibot! We will review the pull request and get back to you soon.

@check-enforcer
Copy link

check-enforcer bot commented Mar 2, 2022

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 python - [service] - ci

@BigCat20196 BigCat20196 changed the title [AutoRelease] t2-sqlvirtualmachine-2022-03-02-66648(Do not merge) [AutoRelease] t2-sqlvirtualmachine-2022-03-02-66648 Mar 4, 2022
@msyyc msyyc merged commit fdaba3a into Azure:main Mar 4, 2022
@msyyc msyyc deleted the t2-sqlvirtualmachine-2022-03-02-66648 branch March 4, 2022 02:01
iscai-msft added a commit to iscai-msft/azure-sdk-for-python that referenced this pull request Mar 4, 2022
@iscai-msft
Merge branch 'main' of https://github.com/Azure/azure-sdk-for-python …
b042273 
…into new_metrics_advisor

* 'main' of https://github.com/Azure/azure-sdk-for-python: (92 commits)
  [Mgmt Compute] Sanitize recordings (Azure#23331)
  [Tables] Release prep (Azure#23297)
  [Cosmos] move system_key logic to query_iterable (Azure#22893)
  [Cosmos] added additional warning to default consistency change (Azure#23225)
  update template (Azure#23333)
  [Storage] Address comments from API Review for March release (Azure#23294)
  code and test (Azure#23273)
  [textanalytics] release prep + fixing docstrings and links (Azure#23315)
  [Schema Registry] rename request kwargs to request options (Azure#23325)
  update new app service api version (Azure#23034)
  [SchemaRegistry] add tests for error codes (Azure#23140)
  Increment package version after release of azure-core (Azure#23319)
  Sync eng/common directory with azure-sdk-tools for PR 2824 (Azure#23314)
  Add python credscan in ci.yml (Azure#23307)
  [SchemaRegistry] avro api changes (Azure#23259)
  [KeyVualt KV] Fix cspell errors (Azure#23255)
  [KeyVault Certs] Fix cspell errors (Azure#23251)
  [AutoRelease] t2-containerregistry-2022-02-21-89653(Do not merge) (Azure#23155)
  [KeyVault Keys] Fix cspell errors (Azure#23250)
  Sync eng/common directory with azure-sdk-tools for PR 2830 (Azure#23267)
  ...
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 7, 2022
@azclibot @rakshith91
code and test (Azure#23273)
92e6774 
Co-authored-by: PythonSdkPipelines <PythonSdkPipelines>
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 10, 2022
@azclibot @rakshith91
code and test (Azure#23273)
79de9f5 
Co-authored-by: PythonSdkPipelines <PythonSdkPipelines>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@msyyc msyyc msyyc approved these changes

@BigCat20196 BigCat20196 Awaiting requested review from BigCat20196

Assignees
No one assigned
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@azclibot @azure-sdk @msyyc