Skip to content

storage-relesae#20353

Merged
qiaozha merged 4 commits intoAzure:mainfrom
colawwj:storage-relesae
Feb 15, 2022
Merged

storage-relesae#20353
qiaozha merged 4 commits intoAzure:mainfrom
colawwj:storage-relesae

Conversation

@colawwj
Copy link
Copy Markdown
Contributor

@colawwj colawwj commented Feb 14, 2022

@ghost ghost added Storage Storage Service (Queues, Blobs, Files) Mgmt This issue is related to a management-plane library. labels Feb 14, 2022
@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 js - [service] - ci

@qiaozha qiaozha closed this Feb 15, 2022
@qiaozha qiaozha reopened this Feb 15, 2022
@qiaozha
Copy link
Copy Markdown
Member

qiaozha commented Feb 15, 2022

/azp run

@azure-pipelines
Copy link
Copy Markdown

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.

@qiaozha qiaozha closed this Feb 15, 2022
@qiaozha qiaozha reopened this Feb 15, 2022
@qiaozha qiaozha merged commit ccc7c3f into Azure:main Feb 15, 2022
@colawwj colawwj deleted the storage-relesae branch May 19, 2022 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Mgmt This issue is related to a management-plane library. Storage Storage Service (Queues, Blobs, Files)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants