Skip to content

59802373 - Don't fail the pipeline for component governance alerts - #5909

Closed
alexlamtest wants to merge 2 commits into
mainfrom
alexlamtest-patch-1
Closed

59802373 - Don't fail the pipeline for component governance alerts#5909
alexlamtest wants to merge 2 commits into
mainfrom
alexlamtest-patch-1

Conversation

@alexlamtest

@alexlamtest alexlamtest commented Oct 16, 2025

Copy link
Copy Markdown
Contributor

This is the recommended configuration from component Governance support folks, such that our pipelines don't break while we wait for an CG alert that we can't fix on our side to go away.
We already previously set failOnAlert to false in WindowsAppSDK-BuildFoundation-AnyCPU-Steps.yml.

--
A microsoft employee must use /azp run to validate using the pipelines below.

WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.

For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

@alexlamtest

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@guimafelipe

Copy link
Copy Markdown
Contributor

Closing this one as this change was in #5919

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.

5 participants