summaryrefslogtreecommitdiff
path: root/lorry-controller.conf
Commit message (Collapse)AuthorAgeFilesLines
* Lorry Controller: increase timeout to 3 daysrobjh/increase-timeoutRobert J. Heywood2020-10-051-1/+1
| | | | | | | | Although running the `git svn fetch` command locally only took 12 hours, the lorry service appears to only get about half way through all of the revisions. This change drastically increases the time out to 3 days.
* Lorry Controller: increase timeout to 16 hours.Rob J. Heywood2020-10-021-1/+1
| | | | | | | | | | The virtualbox svn lorry is having a little trouble bootstrapping. The logs indicate the issue could be the `git svn fetch` task is timing out. This is because the timeout is currently set to 2 hours, but the task appears to take in the region of 10 hours to complete. This change increases the timeout to 16 hours from 2 hours. This ought to be ample time to complete the inital fetch of VirtualBox.
* Revert "Temporarily increase lorry-timeout to allow updating fpc mirror"revert-924322a8Ben Brown2020-09-171-1/+1
| | | This reverts commit 924322a8cff67c75fb4a489b5926c765375c0d21
* Temporarily increase lorry-timeout to allow updating fpc mirrorbwh/misc-fixesBen Hutchings2020-09-161-1/+1
| | | | | | | | The fpc mirror stopped updating in 2017, apparently because git-svn doesn't follow redirections. The current timeout of 7200 seconds (= 2 hours) is not long enough for Lorry to catch up. Change it to 28800 seconds (= 8 hours) which I estimate will be long enough to do so. We can change this back later.
* lorry-controller.conf: Reduce core-lorries interval to 10 minutesPedro Alvarez Piedehierro2017-07-031-1/+1
|
* Add lorry for definitions.git in GitlabPedro Alvarez2017-01-111-0/+15
| | | | Change-Id: Iaa4bf319538f0b3c8cf0ef4a514c9a58011fd424
* Add log4cxx which takes ages to clone first-time, so set timeout to 2HDaniel Silverstone2014-09-091-0/+1
|
* Shorten the interval and re-stagger all the repos to make current ↵Daniel Silverstone2013-04-031-2/+2
| | | | development easier
* Remove mirroring from upstream TroveLars Wirzenius2012-11-161-19/+0
| | | | We do not want this, because we are the ultimate upstream Trove.
* Initial configurationTrove Git Controller2012-11-151-0/+35