This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
mark task as failued if ADO notification fails #77
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
chkeita
approved these changes
Oct 2, 2020
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 of the Pull Request
When notifications related to a report fail, the task that generated the report should be marked as failed
PR Checklist
Info on Pull Request
This traps on the python Exceptions related to configuration errors in ADO notifications and marks the task that generated the report as failed.
Validation Steps Performed
Use an invalid ADO notification config (such as invalid username for assign to), generate a report (such as via
onefuzz debug notification job) and observe that the crash reporting job is marked as failed.