| << Back to previous view |
|
[QB-3465] git retry feature improvement
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 9.0.27 |
| Fix Version/s: | 10.0.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Related to https://track.pmease.com/browse/QB-3224 it would be nice to be able to specify the keywordsin the git plugin, when it should do a retry.
We recently have the problem that git fails with Failed to run command: git fetch --all --tags -q Command return code: 1 Command error output: fatal: git fetch-pack: expected ACK/NAK, got 'ERR upload-pack: not our ref <hash>' fatal: The remote end hung up unexpectedly error: Could not fetch origin which sadly does not state that it should be retried, but this would also work here, but does not contain "fatal:" and "Please try again". So it would be nice to have something where we can put different log keywords in to try again like "Please try again,not our ref" and it would retry on these messages. |
| Comments |
| Comment by AlSt [ 11/Nov/19 03:13 PM ] |
|
I found a pretty neat list of retryable messages: https://github.com/jamiesnape/git-retry/blob/master/git_retry.py#L24-L60
Also I suggest to not retry until infinity and have a max retry of... let's say 5 times or so. |
| Comment by Robin Shen [ 11/Nov/19 11:29 PM ] |
| Thanks for the info. Will get it into QB10 |