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

[Release] sdk/resourcemanager/vmwarecloudsimple/armvmwarecloudsimple/0.1.0 #16632

Conversation

Alancere
Copy link
Contributor

…0.1.0 generation from spec commit: c09b26d4aaa40fb37380aae01b7019b75cff3e34

  • The purpose of this PR is explained in this or a referenced issue.
  • The PR does not update generated files.
  • Tests are included and/or updated for code changes.
  • Updates to CHANGELOG.md are included.
  • MIT license headers are included in each file.

…0.1.0 generation from spec commit: c09b26d4aaa40fb37380aae01b7019b75cff3e34
@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, please perform following steps:

For track 2 SDKs 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 go - [service] - ci

@Alancere
Copy link
Contributor Author

/azp run prepare-pipelines

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Alancere
Copy link
Contributor Author

/azp run go - armvmwarecloudsimple - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Alancere
Copy link
Contributor Author

/azp run go - armvmwarecloudsimple - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@RickWinter RickWinter added the Mgmt This issue is related to a management-plane library. label Dec 13, 2021
@ArcturusZhang
Copy link
Member

/check-enforcer override

@ArcturusZhang ArcturusZhang merged commit 96bb1c4 into Azure:main Dec 23, 2021
jhendrixMSFT pushed a commit to jhendrixMSFT/azure-sdk-for-go that referenced this pull request Jan 12, 2022
…0.1.0 (Azure#16632)

* [Release] sdk/resourcemanager/vmwarecloudsimple/armvmwarecloudsimple/0.1.0 generation from spec commit: c09b26d4aaa40fb37380aae01b7019b75cff3e34

* Update CHANGELOG.md

Co-authored-by: Dapeng Zhang <[email protected]>
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants