Hound Maintenance
Change-Id: Ice50b20a0418a21b5e778c2433132a627ac73146
This commit is contained in:
parent
2bca224b7c
commit
e5f0f8122f
@ -30,3 +30,15 @@ Overview
|
|||||||
Hound is configured to read projects from a config.json file that is
|
Hound is configured to read projects from a config.json file that is
|
||||||
automatically generated from the Gerrit projects.yaml, defined in the
|
automatically generated from the Gerrit projects.yaml, defined in the
|
||||||
$::project_config::jeepyb_project_file variable in Puppet.
|
$::project_config::jeepyb_project_file variable in Puppet.
|
||||||
|
|
||||||
|
|
||||||
|
Maintenance
|
||||||
|
===========
|
||||||
|
|
||||||
|
Hound uses 'git pull' to keep repos in sync. If a force push is ever used to
|
||||||
|
correct an issue in a repo, then hound will not be able to pull or index those
|
||||||
|
changes. The only way to detect this is to look in /var/log/hound.log. The
|
||||||
|
error message looks like hound attempting to update the repo and getting a
|
||||||
|
'remote host hung up' message. The issue can be corrected by an infra-root
|
||||||
|
removing the relevant hound data directory. Hound will re-clone with the new
|
||||||
|
history.
|
||||||
|
Loading…
Reference in New Issue
Block a user