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

[AutoRelease] t2-netapp-2022-01-12-75881 #22467

Merged
merged 2 commits into from
Jan 13, 2022

Conversation

azclibot
Copy link
Contributor

@azclibot azclibot commented Jan 12, 2022

@msyyc
Copy link
Member

msyyc commented Jan 12, 2022

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

ghost commented Jan 12, 2022

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

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

@msyyc msyyc changed the title [AutoRelease] t2-netapp-2022-01-12-75881(Do not merge) [AutoRelease] t2-netapp-2022-01-12-75881 Jan 12, 2022
Copy link
Contributor

@hildurhodd hildurhodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@msyyc msyyc merged commit e14df6c into Azure:main Jan 13, 2022
@msyyc msyyc deleted the t2-netapp-2022-01-12-75881 branch January 13, 2022 02:13
iscai-msft added a commit to iscai-msft/azure-sdk-for-python that referenced this pull request Jan 14, 2022
…into merge_patch

* 'main' of https://github.com/Azure/azure-sdk-for-python: (72 commits)
  [tool]update llc-quick-start-tool for py3 only (Azure#22507)
  [mgmt] update setupy for python3.6 (Azure#22505)
  [pipeline] Upgrade python version to `python3.8` (Azure#22503)
  [AutoRelease] t2-synapse-2022-01-11-70733 (Azure#22439)
  Update tests.md (Azure#22500)
  disable per Azure#22498 (Azure#22499)
  [AnomalyDetector] Release 3.0.0b4 (Azure#22191)
  [translation] update docs to include managed identity option (Azure#22366)
  add back py3.6 (Azure#22478)
  Add Python 3.6 support back to Storage packages (Azure#22483)
  allow Python 3.6 with the sdk (Azure#22456)
  remove hardcoded subscription ID (Azure#22481)
  clean up tests/docs (Azure#22480)
  Increment version for eventhub releases (Azure#22485)
  [Cosmos] Remove support for Python27, set Python36 as minimum, and update cosmos emulator pipeline (Azure#22475)
  Increment version for servicebus releases (Azure#22484)
  add back py3.6 (Azure#22477)
  [AutoRelease] t2-datafactory-2022-01-06-31864 (Azure#22362)
  [AutoRelease] t2-apimanagement-2022-01-06-51326 (Azure#22361)
  [AutoRelease] t2-netapp-2022-01-12-75881 (Azure#22467)
  ...
iscai-msft added a commit to iscai-msft/azure-sdk-for-python that referenced this pull request Jan 18, 2022
…into add_back_error_message

* 'main' of https://github.com/Azure/azure-sdk-for-python: (127 commits)
  [tool]update llc-quick-start-tool for py3 only (Azure#22507)
  [mgmt] update setupy for python3.6 (Azure#22505)
  [pipeline] Upgrade python version to `python3.8` (Azure#22503)
  [AutoRelease] t2-synapse-2022-01-11-70733 (Azure#22439)
  Update tests.md (Azure#22500)
  disable per Azure#22498 (Azure#22499)
  [AnomalyDetector] Release 3.0.0b4 (Azure#22191)
  [translation] update docs to include managed identity option (Azure#22366)
  add back py3.6 (Azure#22478)
  Add Python 3.6 support back to Storage packages (Azure#22483)
  allow Python 3.6 with the sdk (Azure#22456)
  remove hardcoded subscription ID (Azure#22481)
  clean up tests/docs (Azure#22480)
  Increment version for eventhub releases (Azure#22485)
  [Cosmos] Remove support for Python27, set Python36 as minimum, and update cosmos emulator pipeline (Azure#22475)
  Increment version for servicebus releases (Azure#22484)
  add back py3.6 (Azure#22477)
  [AutoRelease] t2-datafactory-2022-01-06-31864 (Azure#22362)
  [AutoRelease] t2-apimanagement-2022-01-06-51326 (Azure#22361)
  [AutoRelease] t2-netapp-2022-01-12-75881 (Azure#22467)
  ...
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 10, 2022
* support py36

* support py36

Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants