Report build errors as errors to Azure DevOps #5016
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is a release management task, as per our policy, we are self-approving it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently the CI build reports all "issues" as warnings to Azure DevOps, so the errors that caused a build to fail aren't easy to find. Previously we had been using Cake.Frosting.Issues.Recipe to automatically report these issues, which does not distinguish between errors and warnings, and that logic was copied when we recently removed the Cake.Frosting.Issues.Recipe package reference during the upgrade to Cake 2.0. This PR adjusts that logic to report errors as errors and everything else as warnings.