Skip to content

Conversation

@kllysng
Copy link
Contributor

@kllysng kllysng commented Dec 19, 2024

With the new task, I've configured the build to:

  • fail if the number of warnings has increased since the previous build - no new warnings!
  • show warning statistics to show the changes in number of warnings grouped by task/code file/object

I have not selected this option:

  • Force fewer warnings
  • Allow Variance - we don't want the number of warnings to creep up.

Build Quality Checks Warnings Policy documentation: https://github.com/MicrosoftPremier/VstsExtensions/blob/master/BuildQualityChecks/en-US/WarningsPolicy.md#evaluateTaskWarnings

@kllysng kllysng requested a review from a team as a code owner December 19, 2024 23:32
Copy link
Collaborator

@jmprieur jmprieur left a comment

Choose a reason for hiding this comment

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

LGTM
Thanks @kellyyangsong

Copy link
Collaborator

@jennyf19 jennyf19 left a comment

Choose a reason for hiding this comment

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

nice
:shipit:

@kllysng kllysng merged commit 191c6ae into master Dec 20, 2024
5 checks passed
@kllysng kllysng deleted the kellysong/warning-policy branch December 20, 2024 18:03
This was referenced Aug 1, 2025
This was referenced Dec 4, 2025
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.

4 participants