Commit 78513bb
Add retry logic to issue comment and close in NotificationService (#2026)
The GitHub API has eventual consistency - a newly created issue may not
be fully propagated across GitHub's backend services when the first
comment or close request arrives. This was observed as an
ApiValidationException ("could not resolve to a node") on the comment
step in build#2925294.
Wrap both the comment creation and issue close calls with the existing
RetryHelper policy (5 retries, jittered exponential backoff) to handle
these transient failures.
Related: dotnet/dotnet-docker-internal#10232
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent db91e0d commit 78513bb
1 file changed
Lines changed: 9 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | | - | |
53 | | - | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
54 | 55 | | |
55 | 56 | | |
56 | 57 | | |
| |||
80 | 81 | | |
81 | 82 | | |
82 | 83 | | |
83 | | - | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
84 | 87 | | |
85 | 88 | | |
86 | 89 | | |
87 | | - | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
88 | 93 | | |
89 | 94 | | |
90 | 95 | | |
| |||
0 commit comments