Skip to content

[AutoRelease] t2-testbase-2021-06-17-62837 - #19288

Merged
Yuchao Yan (msyyc) merged 3 commits into
Azure:masterfrom
azclibot:t2-testbase-2021-06-17-62837
Jun 18, 2021
Merged

[AutoRelease] t2-testbase-2021-06-17-62837#19288
Yuchao Yan (msyyc) merged 3 commits into
Azure:masterfrom
azclibot:t2-testbase-2021-06-17-62837

Conversation

@azclibot

@azclibot Azure CLI Bot (azclibot) commented Jun 17, 2021

Copy link
Copy Markdown
Contributor

SDKAuto and others added 2 commits June 8, 2021 08:51
Copied from Private:RPSaaSMaster (Azure#14710)

Co-authored-by: Bin Yu <biy@microsoft.com>
@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Jun 17, 2021
@ghost

Copy link
Copy Markdown

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

@check-enforcer

Copy link
Copy Markdown

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

@RAY-316 Cassius Smith (RAY-316) changed the title [AutoRelease] t2-testbase-2021-06-17-62837(Do not merge) [AutoRelease] t2-testbase-2021-06-17-62837 Jun 17, 2021
@RAY-316

Copy link
Copy Markdown
Contributor

/azp run prepare-pipelines

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@RAY-316

Copy link
Copy Markdown
Contributor

/azp run python - testbase - ci

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@RAY-316

Copy link
Copy Markdown
Contributor

/azp run prepare-pipelines

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@msyyc
Yuchao Yan (msyyc) merged commit c49ef6a into Azure:master Jun 18, 2021
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