Skip to content

Preparation for Key Vault patch release for August 2021#23529

Merged
vcolin7 merged 2 commits intoAzure:release/keyvault-sdkfrom
vcolin7:keyvault-patch-release-august-2021
Aug 13, 2021
Merged

Preparation for Key Vault patch release for August 2021#23529
vcolin7 merged 2 commits intoAzure:release/keyvault-sdkfrom
vcolin7:keyvault-patch-release-august-2021

Conversation

@vcolin7
Copy link
Member

@vcolin7 vcolin7 commented Aug 12, 2021

No description provided.

@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 java - [service] - ci

## 4.1.0-beta.1 (Unreleased)
## 4.0.2 (2021-08-12)

### Other Changes
Copy link
Member

Choose a reason for hiding this comment

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

Delete this empty section

Copy link
Member Author

Choose a reason for hiding this comment

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

It's not empty, it's a parent header of Dependency Updates.

@vcolin7
Copy link
Member Author

vcolin7 commented Aug 12, 2021

/azp run java - keyvault - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vcolin7 vcolin7 merged commit 4ccf944 into Azure:release/keyvault-sdk Aug 13, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request Apr 12, 2023
[Text Translation] Fixing tspconfig.yaml (Azure#23529)

Co-authored-by: Michal Materna <mimat@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants