Retrying a failed status check starts polling for status check changes
requested to merge 457120-retrying-a-failed-status-check-does-not-refresh-the-current-status-to-the-new-status-without into master
What does this MR do and why?
This MR adds polling for status check changes when we're retrying a status check
Without this change polling will start only on page refresh
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
N/A
How to set up and validate locally
- Setup a status check in
Settings > Merge requests
for some project- You can use https://caphector.com/webhook/test.php for test purposes
- Open new merge request in your project
- Note: for existing merge requests status checks will be stuck in
Pending
state for a long time so it is faster to open a new MR
- Note: for existing merge requests status checks will be stuck in
- Wait for status check to timeout
- Click
retry
. Ensure you're not refreshing page - Observe polling to
status_checks
endpoint in devtools - In ~2mins observe status change to failed without page reload
Related to #457120 (closed)
Edited by Illya Klymov