Clark Boylan 177edc0abb Retry gitea repo setting HTTP POSTs ... I ran our global gitea project sync playbook across all eight gitea hosts and one failed with a 404 against a specific project. Rerunning the playbook against that one gitea server worked fine. Until we sort out why this might happen lets retry our HTTP POSTs up to 3 times until they succeed. Some numbers: We have ~2k repos and 8 servers and make two http requests per repo for a total of 32k requests. If one fails out of that the success rate is very high so retrying a few times should be fine. Change-Id: I937a4f852f6713a419c03a17c3b4984a97eae0d8		2019-03-15 13:01:39 -07:00
..
main.yaml	Filter setup-repos loop before include_tasks	2019-03-04 20:39:17 +00:00
setup-org.yaml	Aggregate all gitea repos and check against them	2019-03-01 20:49:30 -08:00
setup-repo.yaml	Retry gitea repo setting HTTP POSTs	2019-03-15 13:01:39 -07:00