Add retry for clone step

[johnatasr]

Proposed Changes

• Added a retry settings for clone step, allowing repeat the process three times.

Types of Changes

• Drone CI

Verification

Testing

Linked Issues

User-Facing Change

Further Comments

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +4.53 🎉

Comparison is base (882297b) 47.08% compared to head (b1fe26b) 51.61%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7862      +/-   ##
==========================================
+ Coverage   47.08%   51.61%   +4.53%     
==========================================
  Files         143      143              
  Lines       14524    14524              
==========================================
+ Hits         6839     7497     +658     
+ Misses       6593     5844     -749     
- Partials     1092     1183      +91     

Flag	Coverage Δ
e2etests	49.42% <ø> (?)
inttests	44.49% <ø> (+0.04%)	⬆️
unittests	19.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 44 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[brandond]

Is this necessary? If the clone steps fails, there is likely a GitHub outage that will require a re-run of CI pipelines due to other subsequent failures.

[johnatasr]

@brandond Implementing retries for the clone step in CI pipelines can help address temporary network issues, mitigate false failures, and increase overall pipeline stability. While it may not immediately resolve broader issues like a GitHub outage, retrying the clone step increases the chances of successful pipeline execution and contributes to reliable results. What do you think ?

[brandond]

Other than github outages, have we had sufficient problems with the clone step that make this necessary?

[briandowns]

The repeated issues were what inspired the effort. Has happened a number of times with rke2 and k3s over the last few releases but we're overlooked chalking it up to anomalous behavior. This is also part of the effort for more automation and to remove the need for unnecessary manual intervention when a restart is all that's needed.