summaryrefslogtreecommitdiff
path: root/doc/administration/repository_checks.md
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2016-04-12 17:32:58 +0200
committerJacob Vosmaer <contact@jacobvosmaer.nl>2016-04-12 17:32:58 +0200
commitea787165b3a9604aa86304e29778066bb014824e (patch)
treeacaf9cf04c004b43bb87001ddda17a1542fc68bf /doc/administration/repository_checks.md
parent97f4ffff1e7b5da94e18edc20c009ffb46784187 (diff)
downloadgitlab-ce-ea787165b3a9604aa86304e29778066bb014824e.tar.gz
Move 'clear checks' button to applicatoin settings
Diffstat (limited to 'doc/administration/repository_checks.md')
-rw-r--r--doc/administration/repository_checks.md33
1 files changed, 11 insertions, 22 deletions
diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md
index 77f28209f2f..e22b04928cc 100644
--- a/doc/administration/repository_checks.md
+++ b/doc/administration/repository_checks.md
@@ -4,12 +4,13 @@ _**Note:** This feature was [introduced][ce-3232] in GitLab 8.7_
---
-Git has a built-in mechanism [git fsck][git-fsck] to verify the
-integrity of all data commited to a repository. GitLab administrators can
-trigger such a check for a project via the admin panel. The checks run
-asynchronously so it may take a few minutes before the check result is
-visible on the project admin page. If the checks failed you can see their
-output on the admin log page under 'repocheck.log'.
+Git has a built-in mechanism \[git fsck\]\[git-fsck\] to verify the
+integrity of all data commited to a repository. GitLab administrators
+can trigger such a check for a project via the project page under the
+admin panel. The checks run asynchronously so it may take a few minutes
+before the check result is visible on the project admin page. If the
+checks failed you can see their output on the admin log page under
+'repocheck.log'.
## Periodical checks
@@ -22,20 +23,8 @@ than once a day.
## Disabling periodic checks
-You can disable the periodic checks by giving them an empty cron
-schedule in gitlab.yml.
-
-```
-# For omnibus installations, in /etc/gitlab/gitlab.rb:
-gitlab_rails['cron_jobs_repository_check_worker_cron'] = ''
-```
-
-```
-# For installations from source, in config/gitlab.yml:
- cron_jobs:
- repository_check_worker:
- cron: ""
-```
+You can disable the periodic checks on the 'Settings' page of the admin
+panel.
## What to do if a check failed
@@ -47,8 +36,8 @@ resolved the issue use the admin panel to trigger a new repository check on
the project. This will clear the 'check failed' state.
If for some reason the periodical repository check caused a lot of false
-alarms you can choose to clear ALL repository check states from the admin
-project index page.
+alarms you can choose to clear ALL repository check states from the
+'Settings' page of the admin panel.
---
[ce-3232]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3232 "Auto git fsck"