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

Increment version for template releases #15047

Conversation

azure-sdk
Copy link
Collaborator

Increment package version after release of azure_template

@check-enforcer
Copy link

check-enforcer bot commented Nov 5, 2020

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

@azure-sdk azure-sdk force-pushed the sync-eng/common-feature/AddInvokeDevOpsAPI-1161-ForTestPipeline branch 2 times, most recently from a9fbdb2 to f2042b1 Compare November 5, 2020 21:48
@weshaggard
Copy link
Member

@chidozieononiwu I assume this is from your testing?

@azure-sdk azure-sdk force-pushed the sync-eng/common-feature/AddInvokeDevOpsAPI-1161-ForTestPipeline branch from f2042b1 to 7dd5f9f Compare November 12, 2020 19:06
@azure-sdk azure-sdk closed this Nov 16, 2020
@azure-sdk azure-sdk deleted the branch Azure:sync-eng/common-feature/AddInvokeDevOpsAPI-1161-ForTestPipeline November 16, 2020 21:58
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this pull request Jul 1, 2021
Remove files from package which are not part of management plane SDK - update readme.md (Azure#15047)

* Update readme.md

* Update readme.md
@azure-sdk azure-sdk deleted the increment-package-version-template-607117 branch October 19, 2023 01:54
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.

3 participants