[allura:tickets] #7857 Retry svnsync repo clone failures

[Dave Brondsema <da...@brondsema.net>]

- **labels**: sf-current, sf-2 --> sf-2



---

** [tickets:#7857] Retry svnsync repo clone failures**

**Status:** closed
**Milestone:** unreleased
**Labels:** sf-2 
**Created:** Thu Mar 19, 2015 02:57 PM UTC by Dave Brondsema
**Last Updated:** Fri Mar 27, 2015 11:10 AM UTC
**Owner:** Dave Brondsema

Repo clone tasks may fail due to 'svnsync' failing (remote server timeout or random error, etc).  We should be smart about retrying those.  Other failures that are a result of our code can happen too (failure to parse author, or timestamp properly) and it doesn't make sense to retry those.

I don't know about git/hg transfer errors.  SVN seems to be the most common


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.