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

shared_requirements msrest version update #17938

Merged
merged 2 commits into from
Apr 14, 2021
Merged

shared_requirements msrest version update #17938

merged 2 commits into from
Apr 14, 2021

Conversation

RAY-316
Copy link
Contributor

@RAY-316 RAY-316 commented Apr 9, 2021

shared_requirements msrest verison update

@RAY-316 RAY-316 changed the title shared_requirements msrest verison update shared_requirements msrest version update Apr 9, 2021
@check-enforcer
Copy link

check-enforcer bot commented Apr 9, 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 python - [service] - ci

@msyyc
Copy link
Member

msyyc commented Apr 9, 2021

/check-enforcer override

@msyyc msyyc closed this Apr 9, 2021
@msyyc msyyc reopened this Apr 9, 2021
@msyyc
Copy link
Member

msyyc commented Apr 9, 2021

/check-enforcer override

jsntcy
jsntcy requested changes Apr 9, 2021
View reviewed changes
Copy link
Member

@jsntcy jsntcy left a comment

Choose a reason for hiding this comment

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

Hold on to not merge before confirm with @scbedd if this change will not affect other CI jobs.

@msyyc msyyc self-requested a review April 12, 2021 02:33
@jsntcy
Copy link
Member

jsntcy commented Apr 14, 2021

/check-enforcer evaluate

@jsntcy
Copy link
Member

jsntcy commented Apr 14, 2021

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@jsntcy jsntcy closed this Apr 14, 2021
@jsntcy jsntcy reopened this Apr 14, 2021
@jsntcy
Copy link
Member

jsntcy commented Apr 14, 2021

/check-enforcer evaluate

@jsntcy
Copy link
Member

jsntcy commented Apr 14, 2021

/check-enforcer override

@msyyc msyyc merged commit e01a658 into Azure:master Apr 14, 2021
iscai-msft added a commit that referenced this pull request Apr 15, 2021
@iscai-msft
Merge branch 'master' of https://github.com/Azure/azure-sdk-for-python …
3fd484f 
…into protocol_base

* 'master' of https://github.com/Azure/azure-sdk-for-python: (337 commits)
  [Container Registry] adding blurb about env vars to set (#17976)
  shared_requirements msrest verison update (#17938)
  Deprecate Azure-Synapse (#18027)
  add perf tests (#17519)
  Increment package version after release of azure-search-documents (#18017)
  [Communication]: Migrated python identity tests to use ARM template (#17890)
  [Container Registry] fixing up the test-resources-post script (#17883)
  [Communication]: Removed error code assertion from unauthorized phone number test (#17955)
  Add Conda Publishing (#17889)
  fix search fields (#18014)
  Sync eng/common directory with azure-sdk-tools for PR 1552 (#18011)
  [AppConfiguration] fix tests (#17917)
  updating generated code (#17874)
  Update document translation sample slug (#17989)
  update release date (#17988)
  [Communication] - SDK - Synced SMS and Phone Numbers shared folders (#17985)
  Remove unnecessary attribute access (#18007)
  [AutoRelease] t2-healthcareapis-2021-04-12-56802 (#17968)
  Revert retain. (#18004)
  Sync eng/common directory with azure-sdk-tools for PR 1553 (#18002)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jsntcy jsntcy jsntcy approved these changes

@msyyc msyyc msyyc approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@RAY-316 @msyyc @jsntcy