home/gitlabhq
2
0
Fork 0
mirror of https://github.com/wahyd4/gitlabhq.git synced 2026-08-13 14:46:05 +10:00
Code Issues Packages Projects Releases Wiki Activity
8,620 Commits 48 Branches 340 Tags
67eb14d308bfb98d30e44f4e8efdcba60fe2786c
Commit Graph
228 Commits
Author SHA1 Message Date
Dmitriy Zaporozhets dca8f6d4a6 Merge pull request #6492 from tsigo/gitlab-shell-custom-path 
Respect custom gitlab_shell path in gitlab:gitlab_shell:check task
 2014-03-10 17:30:21 +02:00
Robert Speicher c5f76e5939 Popen (at least on OSX) expects an Array, not a String 
This was causing the gitlab:check task to exit prematurely with the
error "System commands must be given as an array of strings."
 2014-03-07 21:39:48 -05:00
Robert Speicher 30f8713aa1 Respect custom gitlab_shell path in gitlab:gitlab_shell:check task 
Prior to this change, if I customized the config value of
`gitlab.gitlab_shell.path`, the check would ignore this value in favor
of `"~<gitlab.gitlab_shell.ssh_user>/gitlab-shell/"` resulting in a
failed check when the configuration was otherwise valid.
 2014-03-07 21:05:56 -05:00
Jacob Vosmaer d6b0ac96f7 Invoke Kernel#system with separate arguments 2014-03-03 08:40:30 +01:00
Jacob Vosmaer 2b816075dc Replace backticks with Gitlab::Popen 2014-03-03 08:40:29 +01:00
Dmitriy Zaporozhets 168e0341a3 Merge pull request #5520 from gabetax/rake_group_bulk_add_permissions 
add rake gitlab:import: all_users_to_all_groups and user_to_groups
 2014-02-12 09:40:40 +02:00
Johannes Schleifenbaum 7085892e47 remove remaining python references 2014-02-03 11:25:47 +01:00
Dmitriy Zaporozhets 9e181d36ea Dont check for python any more 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2014-01-31 13:09:10 +02:00
Dmitriy Zaporozhets 4d56c359d3 Merge pull request #6075 from skv-headless/remove_deprecated_finders 
Remove deprecated finders
 2014-01-22 11:04:56 -08:00
Jacob Vosmaer 2f4d0a3008 Rephrase LDAP check script output 
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.
 2014-01-21 11:05:03 +01:00
dosire 2ddfa882c0 Better wording of the import instructions. 2014-01-20 10:44:40 +01:00
skv a3f645ef51 Remove deprecated finders 2014-01-19 23:39:56 +04:00
Dmitriy Zaporozhets 4d7792bc38 Merge branch 'explain_ldap_check' into 'master' 
Improve the explanation of the LDAP check script
 2014-01-17 14:14:05 +00:00
Dmitriy Zaporozhets efa10c819d Replace context with service in lib 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2014-01-16 20:35:21 +02:00
Jacob Vosmaer af9a14c49c Explain that limit only applies to the check 2014-01-16 18:40:45 +01:00
Dmitriy Zaporozhets 23d180f5f1 Merge branch 'ldap_check' of /home/git/repositories/gitlab/gitlabhq 2013-12-04 14:56:19 +00:00
Jacob Vosmaer 80302a0f6f Limit the number of results in gitlab:ldap:check 2013-12-03 18:51:21 +01:00
Jacob Vosmaer 376cfc6ac6 Give more information in rake gitlab:ldap:check 2013-11-28 18:12:30 +01:00
Jacob Vosmaer 9f4909faad Add LDAP check to rake gitlab:check 2013-11-28 15:20:40 +01:00
Jacob Vosmaer 562a461c56 Disable rake color output unless connected to TTY 2013-11-27 10:09:46 +01:00
Dmitriy Zaporozhets b07c02eb13 Add more info to admin dashboard 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2013-11-20 13:41:41 +02:00
Dmitriy Zaporozhets 7101b22c2e Recommend gitlab-shell 1.7.9 in docs and check task 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2013-11-20 12:34:14 +02:00
Jacob Vosmaer 0ab0ca0d9d Use gitlab-shell 1.7.8 2013-11-14 13:35:45 +01:00
Dmitriy Zaporozhets c28786ecbe Require gitlab-shell 1.7.6 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2013-11-06 21:52:37 +02:00
Gabe Martin-Dempesy 17105038ca add rake gitlab:import: all_users_to_all_groups and user_to_groups 
I opted for admins to be added as "owners" instead of "masters" because project masters can managers members, but only group owners can manage members.
 2013-11-02 17:12:29 -05:00
Dmitriy Zaporozhets 4c47a89fa5 Require gitlab-shell 1.7.4 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2013-11-01 16:58:24 +02:00
Perry Faro 5d98afb55b Fix sidekiq start text in documentation and gitlab:check 2013-11-01 11:52:44 +01:00
Dmitriy Zaporozhets 9ab4539a62 Require gitlab-shell v1.7.3 2013-10-31 19:48:39 +02:00
Jacob Vosmaer 73d19bb320 Count sidekiq processes using String#scan 
It seems there is no easy way to count pattern occurences with
String#match.
 2013-10-17 12:01:29 +02:00
Marin Jankovski f3d77a7661 Add invert match to sidekiq match. 2013-10-16 13:39:09 +02:00
Dmitriy Zaporozhets 3db47d12f2 Merge branch 'check_hooks' of /home/git/repositories/gitlab/gitlabhq 2013-10-07 10:29:00 +00:00
Jacob Vosmaer 99916fe159 Add troubleshooting hints to update hook check 2013-10-07 11:27:38 +02:00
Jacob Vosmaer 4017789f5a Only kill sidekiqs belonging to gitlab user 2013-10-04 11:25:44 +02:00
Dmitriy Zaporozhets e48c6fab60 Make rake gitlab:test works 2013-09-29 23:36:44 +03:00
Dmitriy Zaporozhets 9f8d50e996 gitlab:test rake task now includes jasmine and db setup 2013-09-29 17:43:33 +03:00
Dmitriy Zaporozhets 1df225bb38 Merge pull request #3006 from jweslley/master 
add rake tasks for web hooks management
 2013-09-29 05:24:11 -07:00
Johannes Schleifenbaum b5d7bcb784 [gitlab:check] Fix detecting the status of sidekiq 
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.
 2013-09-27 16:06:06 +02:00
Jacob Vosmaer 1a9b0df767 Check whether only one sidekiq is running 2013-09-27 12:57:05 +02:00
Dmitriy Zaporozhets b6adabb45d Merge branch '6-1-stable' 
Conflicts:
	lib/tasks/gitlab/check.rake
 2013-09-25 18:34:50 +03:00
Jacob Vosmaer ddf873ad5e Add gitlab-shell/bin/check to rake gitlab:check 
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`.
 2013-09-24 14:36:57 +02:00
Hiroyuki Sato a5e19c4edc Update check script 
* GitLab Shell 1.7.1 is required
* Global projects are not supported (refs #5152)
 2013-09-24 15:32:56 +09:00
Marin Jankovski cb6d7e5192 Rescue an error if group doesn't exist 2013-09-12 15:28:46 +02:00
C. Walker 24bc3e0874 Forgot to fix the comment instructions. 2013-09-06 16:45:42 -07:00
C. Walker a9d3e6ce57 Fixed description. 2013-09-06 16:18:09 -07:00
James Newton 4994ebbb11 update gitlab:check to look for update hook, not post-receive 2013-08-27 16:15:32 -05:00
Austin Robertson b74a50451c Fix GitLab Shell version check 2013-08-22 13:10:18 -05:00
Dmitriy Zaporozhets a6e57749dc Use native repo path for import task. Skip wiki repos 2013-08-14 12:45:17 +03:00
Dmitriy Zaporozhets 02e859a234 move backup logic to lib. Fixed removing outdated backups 2013-08-05 12:26:33 +03:00
Johannes Schleifenbaum cd19f82e51 Fix typos 2013-07-29 12:47:06 +02:00
Dmitriy Zaporozhets 475f607a22 Use gitlab-shell authorized_keys truncation. Fix issue with authorized_keys stored in different location 2013-07-18 13:55:01 +03:00