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

[Script] Update Release sdk status #25597

Merged
merged 3 commits into from
Aug 18, 2022
Merged

[Script] Update Release sdk status #25597

merged 3 commits into from
Aug 18, 2022

Conversation

BigCat20196
Copy link
Contributor

@BigCat20196 BigCat20196 commented Aug 8, 2022

No description provided.

@check-enforcer
Copy link

check-enforcer bot commented Aug 8, 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 [Script] Update Auto release debug [Script] Update Release sdk status Aug 9, 2022
@msyyc
Copy link
Member

msyyc commented Aug 18, 2022

/check-enforcer override

@msyyc msyyc merged commit 64f4963 into Azure:main Aug 18, 2022
@msyyc msyyc deleted the release-sdk-status branch August 18, 2022 01:59
wonder6845 pushed a commit to wonder6845/azure-sdk-for-python that referenced this pull request Aug 23, 2022
mccoyp pushed a commit to mccoyp/azure-sdk-for-python that referenced this pull request Sep 22, 2022
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Sep 20, 2023
[Hub Generated] Review request for Microsoft.ContainerService/aks to add version stable/2023-08-01 (Azure#25633)

* Adds base for updating Microsoft.ContainerService/aks from version stable/2023-07-01 to version 2023-08-01

* Updates readme

* Updates API version in new specs and examples

* update (Azure#25468)

* Adding Azure Service Mesh and related changes. (Azure#25482)

* Adding Azure Service Mesh and related changes.

* Fix a typo with api version in examples

* fix a bug with egressGayeways for Istio

* add resourceuid field to managed cluster properties (Azure#25478)

* Adding examples for AzureServiceMesh (Azure#25535)

* Adding an example for AzureServiceMesh

* remove unneeded adonprofiles object

* Adding ingressGateway to the ASM example.

* Adding egressGateways to IstioComponents

* Add egressGateways to the request payload.

* Add BYO CA object to ServiceMeshProfile example

* Fix resource id format for Azure keyvault

* Enrich ASM examples (Azure#25597)

* add asm- prefix to upgrades field on mesh ops (Azure#25601)

---------

Co-authored-by: deveshdama <87668846+deveshdama@users.noreply.github.com>
Co-authored-by: daru__ <ptd2108@columbia.edu>
Co-authored-by: Sanya Kochhar <42152676+SanyaKochhar@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants