allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <d...@brondsema.net>
Subject [allura:tickets] #7857 Retry svnsync repo clone failures
Date Mon, 23 Mar 2015 15:37:31 GMT
- **labels**: sf-current --> sf-current, sf-2



---

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

**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-current sf-2 
**Created:** Thu Mar 19, 2015 02:57 PM UTC by Dave Brondsema
**Last Updated:** Fri Mar 20, 2015 09:39 PM 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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message