An error occurred fetching the project authors.
- 31 May, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 May, 2014 1 commit
-
-
Marin Jankovski authored
-
- 22 May, 2014 1 commit
-
-
Marin Jankovski authored
-
- 27 Apr, 2014 1 commit
-
-
Michael Krane authored
-
- 23 Apr, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 02 Apr, 2014 1 commit
-
-
Marin Jankovski authored
-
- 26 Mar, 2014 1 commit
-
-
Marin Jankovski authored
-
- 21 Mar, 2014 1 commit
-
-
Marin Jankovski authored
-
- 20 Mar, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 Mar, 2014 2 commits
-
-
Jamey J. DeOrio authored
-
Jacob Vosmaer authored
-
- 14 Mar, 2014 3 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 08 Mar, 2014 2 commits
-
-
Robert Speicher authored
This was causing the gitlab:check task to exit prematurely with the error "System commands must be given as an array of strings."
-
Robert Speicher authored
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.
-
- 03 Mar, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 03 Feb, 2014 1 commit
-
-
Johannes Schleifenbaum authored
-
- 31 Jan, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 21 Jan, 2014 1 commit
-
-
Jacob Vosmaer authored
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.
-
- 16 Jan, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 03 Dec, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 28 Nov, 2013 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 20 Nov, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 14 Nov, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 06 Nov, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 01 Nov, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Perry Faro authored
-
- 31 Oct, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 17 Oct, 2013 1 commit
-
-
Jacob Vosmaer authored
It seems there is no easy way to count pattern occurences with String#match.
-
- 16 Oct, 2013 1 commit
-
-
Marin Jankovski authored
-
- 07 Oct, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 04 Oct, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 27 Sep, 2013 2 commits
-
-
Johannes Schleifenbaum authored
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.
-
Jacob Vosmaer authored
-
- 24 Sep, 2013 2 commits
-
-
Jacob Vosmaer authored
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`.
-
Hiroyuki Sato authored
* GitLab Shell 1.7.1 is required * Global projects are not supported (refs #5152)
-
- 12 Sep, 2013 1 commit
-
-
Marin Jankovski authored
-