tree 04121bc8b8ac97f9a65f4a3cd903d3e4e1993501
parent 6860207e32d4e8cb2c6c7efaee2a6f5482e84207
author Antonio Barone <syntonyze@gmail.com> 1678988650 +0100
committer Antonio Barone <syntonyze@gmail.com> 1679485694 +0100

Introduce concept of permanent failure

Currently, when a fetch command fails due to a transport exception it is
always retried (up to maxRetries times).

Whilst there are some cases in which this is the correct thing to do
(transient failures due to network, for example), some errors are
persistent by nature and retrying will lead to another failure.

This is the case, for example, when a fetch fails due to the refs
missing from the remote.

Introduce the concept of permanent failure for which no retries should
be attempted.

Permanent failures currently are:
- SSH exception due to an UnknownHostKey
- The ref being fetched does not exist on the remote

Bug: Issue 16743
Change-Id: I88bdb75e84ea99b1c600d282872304acd3a15466