diff options
author | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-07-30 20:23:59 +0300 |
---|---|---|
committer | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-07-31 15:31:51 +0300 |
commit | 4600265e00baf18f289af19cddb476a5db17f0ea (patch) | |
tree | 0a224fe5b252281bc943b4b186aa13ef858af887 /doc | |
parent | 4702c9f7039c3d4e6e370ef1378cef75cdcaf49a (diff) |
Remove gitlab:user:check_repos task
While reviewing this branch it was noted that this task was broken.
Given the limited value this task brings, and given the fact that much
of the old behaviour has been moved to be automatically fixed, removing
was a good option.
Suggestion in:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20806#note_91261001
Diffstat (limited to 'doc')
-rw-r--r-- | doc/administration/img/raketasks/check_repos_output.png | bin | 19153 -> 0 bytes | |||
-rw-r--r-- | doc/administration/raketasks/check.md | 31 |
2 files changed, 2 insertions, 29 deletions
diff --git a/doc/administration/img/raketasks/check_repos_output.png b/doc/administration/img/raketasks/check_repos_output.png Binary files differdeleted file mode 100644 index 7fda2ba0c0f..00000000000 --- a/doc/administration/img/raketasks/check_repos_output.png +++ /dev/null diff --git a/doc/administration/raketasks/check.md b/doc/administration/raketasks/check.md index a8b4a5cbce3..0ca1d77f1d0 100644 --- a/doc/administration/raketasks/check.md +++ b/doc/administration/raketasks/check.md @@ -1,4 +1,4 @@ -# Check Rake Tasks +# Integrity Check Rake Task ## Repository Integrity @@ -29,7 +29,7 @@ exactly which repositories are causing the trouble. ### Check all GitLab repositories This task loops through all repositories on the GitLab server and runs the -3 integrity checks described previously. +integrity check described previously. **Omnibus Installation** @@ -43,33 +43,6 @@ sudo gitlab-rake gitlab:git:fsck sudo -u git -H bundle exec rake gitlab:git:fsck RAILS_ENV=production ``` -### Check repositories for a specific user - -This task checks all repositories that a specific user has access to. This is important -because sometimes you know which user is experiencing trouble but you don't know -which project might be the cause. - -If the rake task is executed without brackets at the end, you will be prompted -to enter a username. - -**Omnibus Installation** - -```bash -sudo gitlab-rake gitlab:user:check_repos -sudo gitlab-rake gitlab:user:check_repos[<username>] -``` - -**Source Installation** - -```bash -sudo -u git -H bundle exec rake gitlab:user:check_repos RAILS_ENV=production -sudo -u git -H bundle exec rake gitlab:user:check_repos[<username>] RAILS_ENV=production -``` - -Example output: - -![gitlab:user:check_repos output](../img/raketasks/check_repos_output.png) - ## Uploaded Files Integrity Various types of files can be uploaded to a GitLab installation by users. |