Update NotificationConfiguration NuGet package version to 1.0.0-dev.20230216.1 to enable CODEOWNERS regex matcher everywhere
#5488
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
konrad-jamrozik
added
the
Central-EngSys
konrad-jamrozik
changed the title
NotificationConfiguration NuGet package version to 1.0.0-dev.20230216.1NotificationConfiguration NuGet package version to 1.0.0-dev.20230216.1 to enable CODEOWNERS regex matcher everywhere
benbp
approved these changes
Feb 16, 2023
|
/check-enforcer override |
konrad-jamrozik
deleted the
users/kojamroz/update_packages_regex_notif_everywhere
branch
This was referenced Feb 16, 2023
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.
Relevant Teams announcement on Engineering Systems channel
This PR is a follow-up to:
NotificationConfigurationpackage to20230214.1to enableCODEOWNERSregex matcher to default totrue#5452As in subject; the following PR gets deployed with this change:
As a result, all build failure notification recipients will be determined based on the new regex-based, wildcard-supporting
CODEOWNERSmatcher, as opposed to the obsolete prefix-based one.As a result, after this PR is merged, the next run of the pipeline
automation - build-failure-notification-subscriptionswill change the build failure notification recipients.The pipeline run that changed the failure recipients:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2196646&view=logs&j=ad5747fc-b58e-5e0d-2246-f6c6b542e026
Comment explaining how to interpret the log
Relevant tool doc is here:
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/63/Subscribe-to-Notifications
Related work: