Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | | remove remaining python references | Johannes Schleifenbaum | 2014-02-03 | 1 | -46/+0 | |
| | | ||||||
* | | Dont check for python any more | Dmitriy Zaporozhets | 2014-01-31 | 1 | -2/+0 | |
| | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | | Merge pull request #6075 from skv-headless/remove_deprecated_finders | Dmitriy Zaporozhets | 2014-01-22 | 3 | -4/+4 | |
|\ \ | | | | | | | Remove deprecated finders | |||||
| * | | Remove deprecated finders | skv | 2014-01-19 | 3 | -4/+4 | |
| | | | ||||||
* | | | Rephrase LDAP check script output | Jacob Vosmaer | 2014-01-21 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | | | | | | | | | | The previous phrasing lead some people to believe that there is a limit on the number of LDAP users that can sign in to a GitLab instance. That is not the case; the limit in the check script only applies to the diagnostic information result set, so that running `rake gitlab:check` does not output thousands of LDAP users. | |||||
* | | | Better wording of the import instructions. | dosire | 2014-01-20 | 1 | -4/+4 | |
| | | | ||||||
* | | | Merge branch 'explain_ldap_check' into 'master' | Dmitriy Zaporozhets | 2014-01-17 | 1 | -0/+2 | |
|\ \ \ | |/ / |/| | | | | | Improve the explanation of the LDAP check script | |||||
| * | | Explain that `limit` only applies to the check | Jacob Vosmaer | 2014-01-16 | 1 | -0/+2 | |
| | | | ||||||
* | | | Replace context with service in lib | Dmitriy Zaporozhets | 2014-01-16 | 1 | -1/+1 | |
|/ / | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | | Merge branch 'ldap_check' of /home/git/repositories/gitlab/gitlabhq | Dmitriy Zaporozhets | 2013-12-04 | 1 | -0/+39 | |
|\ \ | ||||||
| * | | Limit the number of results in gitlab:ldap:check | Jacob Vosmaer | 2013-12-03 | 1 | -5/+6 | |
| | | | ||||||
| * | | Give more information in rake gitlab:ldap:check | Jacob Vosmaer | 2013-11-28 | 1 | -3/+5 | |
| | | | ||||||
| * | | Add LDAP check to rake gitlab:check | Jacob Vosmaer | 2013-11-28 | 1 | -0/+36 | |
| | | | ||||||
* | | | Disable rake color output unless connected to TTY | Jacob Vosmaer | 2013-11-27 | 1 | -0/+10 | |
|/ / | ||||||
* | | Add more info to admin dashboard | Dmitriy Zaporozhets | 2013-11-20 | 1 | -4/+1 | |
| | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | | Recommend gitlab-shell 1.7.9 in docs and check task | Dmitriy Zaporozhets | 2013-11-20 | 1 | -1/+1 | |
| | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | | Use gitlab-shell 1.7.8 | Jacob Vosmaer | 2013-11-14 | 1 | -1/+1 | |
| | | ||||||
* | | Require gitlab-shell 1.7.6 | Dmitriy Zaporozhets | 2013-11-06 | 1 | -1/+1 | |
|/ | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | Require gitlab-shell 1.7.4 | Dmitriy Zaporozhets | 2013-11-01 | 1 | -1/+1 | |
| | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||||
* | Fix sidekiq start text in documentation and gitlab:check | Perry Faro | 2013-11-01 | 1 | -1/+1 | |
| | ||||||
* | Require gitlab-shell v1.7.3 | Dmitriy Zaporozhets | 2013-10-31 | 1 | -1/+1 | |
| | ||||||
* | Restore sidekiq rake tasks | Jacob Vosmaer | 2013-10-25 | 1 | -2/+4 | |
| | ||||||
* | Count sidekiq processes using String#scan | Jacob Vosmaer | 2013-10-17 | 1 | -7/+7 | |
| | | | | | It seems there is no easy way to count pattern occurences with String#match. | |||||
* | Add invert match to sidekiq match. | Marin Jankovski | 2013-10-16 | 1 | -1/+1 | |
| | ||||||
* | Move unicorn and sidekiq commands into bash script | Jacob Vosmaer | 2013-10-15 | 1 | -20/+7 | |
| | ||||||
* | Use built-in sidekiq deamonization | Jacob Vosmaer | 2013-10-09 | 1 | -1/+1 | |
| | ||||||
* | Remove duplicate log path generation | Jacob Vosmaer | 2013-10-09 | 1 | -2/+6 | |
| | ||||||
* | Always shut down sidekiq before starting | Jacob Vosmaer | 2013-10-09 | 1 | -1/+9 | |
| | ||||||
* | Merge branch 'check_hooks' of /home/git/repositories/gitlab/gitlabhq | Dmitriy Zaporozhets | 2013-10-07 | 1 | -6/+12 | |
|\ | ||||||
| * | Add troubleshooting hints to update hook check | Jacob Vosmaer | 2013-10-07 | 1 | -6/+12 | |
| | | ||||||
* | | Only kill sidekiqs belonging to gitlab user | Jacob Vosmaer | 2013-10-04 | 1 | -4/+6 | |
|/ | ||||||
* | Make rake gitlab:test works | Dmitriy Zaporozhets | 2013-09-29 | 1 | -6/+13 | |
| | ||||||
* | Use gitlab:test for travis-ci | Dmitriy Zaporozhets | 2013-09-29 | 1 | -5/+0 | |
| | ||||||
* | gitlab:test rake task now includes jasmine and db setup | Dmitriy Zaporozhets | 2013-09-29 | 1 | -2/+9 | |
| | ||||||
* | Merge pull request #3006 from jweslley/master | Dmitriy Zaporozhets | 2013-09-29 | 1 | -0/+65 | |
|\ | | | | | add rake tasks for web hooks management | |||||
| * | add rake tasks for web hooks management | Jonhnny Weslley | 2013-02-15 | 1 | -0/+65 | |
| | | ||||||
* | | [gitlab:check] Fix detecting the status of sidekiq | Johannes Schleifenbaum | 2013-09-27 | 1 | -2/+1 | |
| | | | | | | | | | | | | | | | | | | If you are running another sidekiq instance on your server, e.g. GitLab CI, the check script would parse the output of `ps aux` searching for `sidekiq` and returning success, although the GitLab sidekiq may not be running. Now the `ps` call will only print the processes run by the GitLab user. | |||||
* | | Check whether only one sidekiq is running | Jacob Vosmaer | 2013-09-27 | 1 | -1/+26 | |
| | | ||||||
* | | Merge branch '6-1-stable' | Dmitriy Zaporozhets | 2013-09-25 | 1 | -1/+28 | |
|\ \ | | | | | | | | | | | | | Conflicts: lib/tasks/gitlab/check.rake | |||||
| * | | Update check script | Hiroyuki Sato | 2013-09-24 | 1 | -1/+28 | |
| | | | | | | | | | | | | | | | * GitLab Shell 1.7.1 is required * Global projects are not supported (refs #5152) | |||||
* | | | Add gitlab-shell/bin/check to rake gitlab:check | Jacob Vosmaer | 2013-09-24 | 1 | -0/+18 | |
|/ / | | | | | | | | | | | | | We sometimes encounter connectivity issues where gitlab-shell cannot make API calls to the Rails application. There is a self-test script `gitlab-shell/bin/check` that tries to connect to the API; this commit runs that script as part of `rake gitlab:check`. | |||||
* | | Rescue an error if group doesn't exist | Marin Jankovski | 2013-09-12 | 2 | -3/+9 | |
| | | ||||||
* | | Forgot to fix the comment instructions. | C. Walker | 2013-09-06 | 1 | -1/+1 | |
| | | ||||||
* | | Fixed description. | C. Walker | 2013-09-06 | 1 | -1/+1 | |
| | | ||||||
* | | update gitlab:check to look for update hook, not post-receive | James Newton | 2013-08-27 | 1 | -8/+8 | |
| | | ||||||
* | | Remove old migration tasks | Dmitriy Zaporozhets | 2013-08-26 | 7 | -110/+0 | |
| | | | | | | | | | | | | You should update to 6.0 before proceed with update to higher version. So its no reason to keep old tasks any more. It should be still available in 6-0-stable but not in master | |||||
* | | Set iid in fixtures. Add rake dev:setup for development | Dmitriy Zaporozhets | 2013-08-26 | 1 | -0/+10 | |
| | | ||||||
* | | Fix GitLab Shell version check | Austin Robertson | 2013-08-22 | 1 | -1/+1 | |
| | | ||||||
* | | Add iids to milestones. Moved iids logic to separate concern | Dmitriy Zaporozhets | 2013-08-21 | 1 | -0/+15 | |
| | | ||||||
* | | Fix migrate_iids for issues | Dmitriy Zaporozhets | 2013-08-20 | 1 | -1/+1 | |
| | |