Clark Boylan f1bcb6a586 Set a gerrit replication timeout of 15 minutes ... We are seeing that replication tasks occasionally sit around forever and have had to take manual intervention. One theory is that this is related to networking between the gerrit server and the gitea servers. We don't set maxRetries which means replication should be retried infinitely which means if we hit the timeout we should try again. 15 minutes was sort of arbitrarily chosen as ~twice the time it takes to clone a large repo like nova. Change-Id: Iec2536ad149a2e625a1f0107b9fcee3079493607		2021-09-15 16:25:04 -07:00
..
docker-compose.yaml.j2	Remove the mysql support from our gerrit role and image	2021-08-10 13:06:54 -07:00
gerrit.config.j2	gerrit: enable plugin reload in dev mode	2021-05-03 22:37:55 +00:00
gerrit.vhost.j2	Add X-Forwarded-Proto to gerrit apache config	2020-11-21 10:09:35 -08:00
infra_lp_creds.j2	gerrit: fix Launchpad credentials write	2021-07-20 10:54:22 +10:00
jgit.config.j2	Enable git protocol v2 on gerrit	2020-12-09 15:51:10 -08:00
manage-projects.j2	Stop managing gerrit's local git mirror dir	2020-10-16 09:41:07 -07:00
projects.ini.j2	Stop managing gerrit's local git mirror dir	2020-10-16 09:41:07 -07:00
redirect.vhost.j2	Use LE certs for Apache	2020-02-13 10:31:59 -06:00
replication.config.j2	Set a gerrit replication timeout of 15 minutes	2021-09-15 16:25:04 -07:00
root.my.cnf.mariadb_container.j2	gerrit: add mariadb_container option	2021-06-16 13:57:13 +10:00
root.my.cnf.mysql.j2	gerrit: add mariadb_container option	2021-06-16 13:57:13 +10:00
secure.config.j2	Remove the mysql support from our gerrit role and image	2021-08-10 13:06:54 -07:00