home/gitlabhq
2
0
Fork 0
mirror of https://github.com/wahyd4/gitlabhq.git synced 2026-08-15 07:36:41 +10:00
Code Issues Packages Projects Releases Wiki Activity
8,915 Commits 48 Branches 340 Tags
a7aacb4dc4d2cb3875db22dee830553462100a20
Commit Graph
100 Commits
Author SHA1 Message Date
Marin Jankovski 895c913247 Use the latest tag, 1.9.1 for gitlab-shell. 2014-03-21 12:42:59 +01:00
Dmitriy Zaporozhets e013be10d7 GitLab requires gitlab-shell v1.9.0 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2014-03-20 13:37:35 +02:00
Jacob Vosmaer acaf297846 Merge pull request #5993 from DarkHorseComics/bypass-commented-sqlite 
Explain what to do about legacy sqlite in database.yml
 2014-03-18 10:48:27 +01:00
Dmitriy Zaporozhets 8fa53ce43d Merge branch 'check_orphaned_users_groups' into 'master' 
Check Orphaned Users Groups
 2014-03-18 07:14:08 +00:00
Jamey J. DeOrio 37192d5e18 Add more descriptive line for resolving sqlite error during check 2014-03-17 09:43:27 -07:00
Jacob Vosmaer 5e7e814e81 Drop UsersGroup orphans using rails runner 2014-03-17 14:42:20 +01:00
Jacob Vosmaer 4aa3ce7534 Add check for orphaned UsersGroups 2014-03-14 17:25:11 +01:00
Jacob Vosmaer 090ed21e6f Batch key import requires gitlab-shell 1.8.5 2014-03-14 15:58:47 +01:00
Dmitriy Zaporozhets bce8edbbcc Require gitlab-shell v1.8.4 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
 2014-03-14 12:57:26 +02:00
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 2b816075dc Replace backticks with Gitlab::Popen 2014-03-03 08:40:29 +01: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
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
Jacob Vosmaer af9a14c49c Explain that limit only applies to the check 2014-01-16 18:40:45 +01: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
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
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
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
James Newton 4994ebbb11 update gitlab:check to look for update hook, not post-receive 2013-08-27 16:15:32 -05: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
Dmitriy Zaporozhets 5768f98d8d Require gitlab-shell 1.6.0 2013-07-16 21:39:39 +03:00
Dmitriy Zaporozhets 9a0e7c0e85 Merge pull request #4224 from hiroponz/fix-abort-gitlab-app-check 
Fix abort gitlab:app:check
 2013-06-11 01:48:18 -07:00
Sato Hiroyuki c18564d2cb Fix abort gitlab:app:check 
When the file that pointed git bin_path in gitlab.yml dose'nt exist,
bundle rake gitlab:app:check would be aborted.

refs #4205
 2013-06-06 10:10:51 +09:00
Axilleas Pipinellis ff7e808043 Read init script recipe from Rails.root path. Fix #4174 
Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>
 2013-06-05 01:23:28 +03:00
bassrock 3db67ff09c Update check.rake 2013-05-27 13:30:54 -06:00
Dmitriy Zaporozhets 76ffd11684 Merge pull request #3964 from mhfan/improve-sidekiq-check 
improve regrex for match(sidekiq) robustness
 2013-05-23 02:27:34 -07:00
Ben Bodenmiller de29a424e6 changed Gitlab to GitLab 2013-05-19 02:13:39 -07:00
MeiHui FAN dfe082fa1d improve regrex for match(sidekiq) robustness 
e.g.: the sidekiq in my Debian box is v2.11.1
 2013-05-16 17:26:15 +08:00
Sato Hiroyuki 06805fff14 Config setting should be used in git version check. 2013-05-14 19:55:08 +09:00
Sato Hiroyuki 862e0ff6b8 Add Gitlab::VersionInfo class to fix and simplify version check. 
It returns "yes" if required version is "1.7.10" and current version is "1.6.10",
because the patch version of current version equals to that of required version.
 2013-05-08 17:36:48 +09:00