[SERVER-81833] Add retries when pushing single architecture tags as part of mongo-container pipeline Created: 04/Oct/23 Updated: 19/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Zack Winter | Assignee: | Zack Winter |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
Currently there's no retry mechanism built into the mongo-container pipeline's push step. This results in failures due to network flakiness. Add in a retry option since there isn't likely to be any other way to improve this. See BF-30221 for an example of this |