| << Back to previous view |
|
[QB-3224] Quickbuild should retry git fetch command, if suggested by error message
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 8.0.10 |
| Fix Version/s: | 9.0.0 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Sometimes, more or less often, git fetch command executed by quickbuild fails with the following error message/response:
> 2018-07-12 09:43:48 - Failed to run command: git fetch --all --tags -q > Command return code: 1 > Command error output: fatal: git fetch-pack: expected ACK/NAK, got 'A ref was requested that is no longer valid. The ref may have been updated while the git-upload-pack request was received. Please try again.' > fatal: The remote end hung up unexpectedly > error: Could not fetch origin This is caused by the nature of the http(s) request used by git and modifications during these, which occurs more likely with increased action on a repository. Quickbuild should follow the advice in the response and retry the fetch command automatically to avoid failures during CHECK_BUILD_CONDITION. Basically this would make sense for every git command. If there is a "Please try again" contained in the message it really should try the command again. |
| Comments |
| Comment by AlSt [ 20/Aug/18 11:02 AM ] |
| Any thoughts on this one? |
| Comment by Robin Shen [ 20/Aug/18 11:59 AM ] |
| We plan to get this into next big version of QB planned to be released in the end of this year. |