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

[Test] Updates to devtools utils for storage/tables #19040

Merged
21 commits merged into from
Jun 29, 2021
Merged

[Test] Updates to devtools utils for storage/tables #19040

21 commits merged into from
Jun 29, 2021

Conversation

seankane-msft
Copy link
Member

No description provided.

@ghost ghost added Storage Storage Service (Queues, Blobs, Files) Tables labels Jun 2, 2021
@seankane-msft seankane-msft self-assigned this Jun 2, 2021
@seankane-msft seankane-msft requested a review from scbedd June 2, 2021 17:15
@seankane-msft seankane-msft changed the title adding two multi-use objects, adding readme [Test] Updates to devtools utils for storage/tables Jun 2, 2021
@seankane-msft
Copy link
Member Author

/check-enforcer reset

@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

@seankane-msft
Copy link
Member Author

/check-enforcer reset

Copy link
Member

@scbedd scbedd left a comment

Choose a reason for hiding this comment

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

This looks like a really nice cleanup Sean.

@seankane-msft
Copy link
Member Author

/check-enforcer override

@ghost
Copy link

ghost commented Jun 29, 2021

Hello @seankane-msft!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit 20e5bdc into main Jun 29, 2021
@ghost ghost deleted the devtools-upgrade branch June 29, 2021 19:31
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files) Tables
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants