Skip to content

Conversation

@g2vinay
Copy link
Member

@g2vinay g2vinay commented Jun 3, 2021

No description provided.

@ghost ghost added the Azure.Identity label Jun 3, 2021
@g2vinay g2vinay requested review from anuchandy and jianghaolu June 15, 2021 20:06
@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

@g2vinay g2vinay merged commit 23135a5 into Azure:main Jul 28, 2021
ChrisKian added a commit to ChrisKian/liferay-portal that referenced this pull request Jun 9, 2022
…identity to 1.3.6+. azure-identity 1.3.4+ removes the dependency on KeePass (see Azure/azure-sdk-for-java#22063) which had a dependency on com.google.guava-19.  CVE-2018-10237 is only vulnerable when using com.google.guava, so by using azure-sdk-bom 1.0.4+, we avoid the vulnerability.
shuyangzhou pushed a commit to shuyangzhou/liferay-portal that referenced this pull request Jun 27, 2022
…identity to 1.3.6+. azure-identity 1.3.4+ removes the dependency on KeePass (see Azure/azure-sdk-for-java#22063) which had a dependency on com.google.guava-19.  CVE-2018-10237 is only vulnerable when using com.google.guava, so by using azure-sdk-bom 1.0.4+, we avoid the vulnerability.
brianchandotcom pushed a commit to brianchandotcom/liferay-portal that referenced this pull request Jun 27, 2022
…identity to 1.3.6+. azure-identity 1.3.4+ removes the dependency on KeePass (see Azure/azure-sdk-for-java#22063) which had a dependency on com.google.guava-19.  CVE-2018-10237 is only vulnerable when using com.google.guava, so by using azure-sdk-bom 1.0.4+, we avoid the vulnerability.
@g2vinay g2vinay deleted the remove-keepass-identity branch July 13, 2023 01:56
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