delta/gitlab/gitlab-ce.git/lib/tasks, branch commit-status-permission-update

Improve readability of 'rake cache:clear' code

2016-02-19T13:18:57+00:00

Merge branch 'master' of https://gitlab.com/gitlab-org/gitlab-ce into cache-clear

2016-02-18T18:51:58+00:00

Use SCAN during 'rake cache:clear'

2016-02-18T15:55:19+00:00

This allows 'rake cache:clear' to delete millions of keys without
choking. It requires Redis 2.8.0 or newer but we needed that already
anyway.

Remove remaining sqlite method call

2016-02-17T18:34:54+00:00

Remove sqlite check in raketask

2016-02-10T14:54:15+00:00

Prevent StateMachine warnings from outputting during a cron task

2016-01-15T22:47:56+00:00

[ci skip]

Closes #5931

Disable colorization if STDOUT is not a tty

2016-01-13T02:34:23+00:00

Suggest prefacing find command with sudo when base permissions are wrong

2016-01-05T13:30:01+00:00

Closes #5872

Merge branch 'add_user_repo_integrity_rake_task' into 'master'

2015-12-15T18:36:28+00:00


Add user repository integrity check rake task

Corrupt repositories and stuck lock files can cause weird issues in
GitLab. Often we know which user is having these problems and then we
have to go hunt down which repository is causing it. Several times
recently that involved me running queries in the rails console to get
an array of projects and then writing a quick Ruby script to loop
through and run `git fsck`. This last time I also had to check for the
existence of `config.lock` and ref lock files. 

This rake task will eliminate all of those steps and allow an admin to
simply specify a username.

I also added the lock file checks to the existing `gitlab:repo:check`
task which goes through all projects. 

See merge request !2080

[ci skip] Add user repository integrity check rake task

2015-12-14T21:27:14+00:00