using self contained guardian package (#5212) #5712
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
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.
Description
This change updates the release/3.x guardian tools to match those used in master.
The version of Guardian used in the release/3.x branch depends on netcore2.2. Azure DevOps hosted pools recently dropped default support for .NET Core 2.2. Current builds running in that set are now failling.
See also #5168
Customer Impact
All 3.x builds with SDL enabled are currently failing.
Regression
No
Risk
Low. Guardian is run as a separate analysis of the repository artifacts. The product itself should not be affected.
Workarounds
An alternative is to add a task to explicitly install .NET Core 2.2 and continue using the older version of Guardian.