summaryrefslogtreecommitdiff
path: root/lib/tasks
Commit message (Collapse)AuthorAgeFilesLines
...
* | remove remaining python referencesJohannes Schleifenbaum2014-02-031-46/+0
| |
* | Dont check for python any moreDmitriy Zaporozhets2014-01-311-2/+0
| | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Merge pull request #6075 from skv-headless/remove_deprecated_findersDmitriy Zaporozhets2014-01-223-4/+4
|\ \ | | | | | | Remove deprecated finders
| * | Remove deprecated findersskv2014-01-193-4/+4
| | |
* | | Rephrase LDAP check script outputJacob Vosmaer2014-01-211-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.dosire2014-01-201-4/+4
| | |
* | | Merge branch 'explain_ldap_check' into 'master'Dmitriy Zaporozhets2014-01-171-0/+2
|\ \ \ | |/ / |/| | | | | Improve the explanation of the LDAP check script
| * | Explain that `limit` only applies to the checkJacob Vosmaer2014-01-161-0/+2
| | |
* | | Replace context with service in libDmitriy Zaporozhets2014-01-161-1/+1
|/ / | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Merge branch 'ldap_check' of /home/git/repositories/gitlab/gitlabhqDmitriy Zaporozhets2013-12-041-0/+39
|\ \
| * | Limit the number of results in gitlab:ldap:checkJacob Vosmaer2013-12-031-5/+6
| | |
| * | Give more information in rake gitlab:ldap:checkJacob Vosmaer2013-11-281-3/+5
| | |
| * | Add LDAP check to rake gitlab:checkJacob Vosmaer2013-11-281-0/+36
| | |
* | | Disable rake color output unless connected to TTYJacob Vosmaer2013-11-271-0/+10
|/ /
* | Add more info to admin dashboardDmitriy Zaporozhets2013-11-201-4/+1
| | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Recommend gitlab-shell 1.7.9 in docs and check taskDmitriy Zaporozhets2013-11-201-1/+1
| | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Use gitlab-shell 1.7.8Jacob Vosmaer2013-11-141-1/+1
| |
* | Require gitlab-shell 1.7.6Dmitriy Zaporozhets2013-11-061-1/+1
|/ | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Require gitlab-shell 1.7.4Dmitriy Zaporozhets2013-11-011-1/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Fix sidekiq start text in documentation and gitlab:checkPerry Faro2013-11-011-1/+1
|
* Require gitlab-shell v1.7.3Dmitriy Zaporozhets2013-10-311-1/+1
|
* Restore sidekiq rake tasksJacob Vosmaer2013-10-251-2/+4
|
* Count sidekiq processes using String#scanJacob Vosmaer2013-10-171-7/+7
| | | | | It seems there is no easy way to count pattern occurences with String#match.
* Add invert match to sidekiq match.Marin Jankovski2013-10-161-1/+1
|
* Move unicorn and sidekiq commands into bash scriptJacob Vosmaer2013-10-151-20/+7
|
* Use built-in sidekiq deamonizationJacob Vosmaer2013-10-091-1/+1
|
* Remove duplicate log path generationJacob Vosmaer2013-10-091-2/+6
|
* Always shut down sidekiq before startingJacob Vosmaer2013-10-091-1/+9
|
* Merge branch 'check_hooks' of /home/git/repositories/gitlab/gitlabhqDmitriy Zaporozhets2013-10-071-6/+12
|\
| * Add troubleshooting hints to update hook checkJacob Vosmaer2013-10-071-6/+12
| |
* | Only kill sidekiqs belonging to gitlab userJacob Vosmaer2013-10-041-4/+6
|/
* Make rake gitlab:test worksDmitriy Zaporozhets2013-09-291-6/+13
|
* Use gitlab:test for travis-ciDmitriy Zaporozhets2013-09-291-5/+0
|
* gitlab:test rake task now includes jasmine and db setupDmitriy Zaporozhets2013-09-291-2/+9
|
* Merge pull request #3006 from jweslley/masterDmitriy Zaporozhets2013-09-291-0/+65
|\ | | | | add rake tasks for web hooks management
| * add rake tasks for web hooks managementJonhnny Weslley2013-02-151-0/+65
| |
* | [gitlab:check] Fix detecting the status of sidekiqJohannes Schleifenbaum2013-09-271-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 runningJacob Vosmaer2013-09-271-1/+26
| |
* | Merge branch '6-1-stable'Dmitriy Zaporozhets2013-09-251-1/+28
|\ \ | | | | | | | | | | | | Conflicts: lib/tasks/gitlab/check.rake
| * | Update check scriptHiroyuki Sato2013-09-241-1/+28
| | | | | | | | | | | | | | | * GitLab Shell 1.7.1 is required * Global projects are not supported (refs #5152)
* | | Add gitlab-shell/bin/check to rake gitlab:checkJacob Vosmaer2013-09-241-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 existMarin Jankovski2013-09-122-3/+9
| |
* | Forgot to fix the comment instructions.C. Walker2013-09-061-1/+1
| |
* | Fixed description.C. Walker2013-09-061-1/+1
| |
* | update gitlab:check to look for update hook, not post-receiveJames Newton2013-08-271-8/+8
| |
* | Remove old migration tasksDmitriy Zaporozhets2013-08-267-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 developmentDmitriy Zaporozhets2013-08-261-0/+10
| |
* | Fix GitLab Shell version checkAustin Robertson2013-08-221-1/+1
| |
* | Add iids to milestones. Moved iids logic to separate concernDmitriy Zaporozhets2013-08-211-0/+15
| |
* | Fix migrate_iids for issuesDmitriy Zaporozhets2013-08-201-1/+1
| |