25de34e908
The replication, manage-plugins, and delete-project plugins all seem to want to write content out to /var/gerrit/data within the Gerrit container. At /home/gerrit2/review_site/data we've got an old carried over dir from previous installations but this does not appear to be bind mounted. Best I can tell the replication plugin may use this disk location to keep track of tasks that are queued,running,etc and this may work around the issues with autoreloading gerrit replication configs. However, we don't get those benefits when we delete the container (as with docker-compose down/up-d) as the content is ephemeral within the container. Address this by bind mounting the location along with the other bind mounts. Note I have excluded this from backups as I think we don't need backups of things like replication queues. That said depending on what the other plugins use this for we may need to refine our backup rules in the future. Change-Id: If3a91aeb1bd86c8514179b8ecfde17e98c29af6a |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| handlers | ||
| tasks | ||
| templates | ||
| README.rst | ||
Run Gerrit.
This role deploys MariaDB alongside the Gerrit service using docker-compose to run both services in docker containers. Variables below configure MariaDB connection details.
Role Variables