- 11 3月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 08 3月, 2019 1 次提交
-
-
由 Stan Hu 提交于
Until we solve https://gitlab.com/gitlab-com/gitlab-docs/issues/347, let's just be explicit to avoid confusion.
-
- 06 3月, 2019 2 次提交
-
-
由 Takuya Noguchi 提交于
Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>
-
由 Martin Melka 提交于
-
- 05 3月, 2019 3 次提交
-
-
由 Moritz Bellach 提交于
-
由 Nick Thomas 提交于
Sidekiq jobs frequently spawn long-lived child processes to do work. In some circumstances, these can be reparented to init when sidekiq is terminated, leading to duplication of work and strange concurrency problems. This commit changes sidekiq so that, if run as a process group leader, it will forward `INT` and `TERM` signals to the whole process group. If the memory killer is active, it will also use the process group when resorting to `kill -9` to shut down. These changes mean that a naive `kill <pid-of-sidekiq>` will now do the right thing, killing any child processes spawned by sidekiq, as long as the process supervisor placed it in its own process group. If sidekiq isn't a process group leader, this new code is skipped.
-
由 Drew Blessing 提交于
We've previously exposed ca_file and ssl_version but there are many possible options that can be used inside tls_options. Instead of exposing individual ones, simply expose the entire hash so it can be passed in and we won't have to add things in the future.
-
- 04 3月, 2019 2 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Marcel Amirault 提交于
-
- 02 3月, 2019 1 次提交
-
-
由 Stan Hu 提交于
This brings back some of the changes in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20339. For users using Gitaly on top of NFS, accessing the Git data directly via Rugged is more performant than Gitaly. This merge request introduces the feature flag `rugged_find_commit` to activate Rugged paths. There are also Rake tasks `gitlab:features:enable_rugged` and `gitlab:features:disable_rugged` to enable/disable these feature flags altogether. Part of four Rugged changes identified in https://gitlab.com/gitlab-org/gitlab-ce/issues/57317.
-
- 27 2月, 2019 1 次提交
-
-
由 Stan Hu 提交于
As mentioned in https://gitlab.com/gitlab-org/gitlab-ce/issues/58121#note_145299901, it wasn't obvious that upgrading an GitLab HA cluster required special care. Link to the Omnibus documentation for upgrade instructions. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58121
-
- 25 2月, 2019 1 次提交
-
-
由 Takuya Noguchi 提交于
Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>
-
- 23 2月, 2019 1 次提交
-
-
由 Evan Read 提交于
-
- 22 2月, 2019 1 次提交
-
-
由 Evan Read 提交于
Markdown renderers find it easier to determine where lists start and end when lists are surrounded by new lines. For consistency, also ensure entries in the list are aligned when they span multipls lines.
-
- 21 2月, 2019 4 次提交
-
-
由 Marcia Ramos 提交于
- Fix "introduced in" note - Add missing links - Remove unnecessary hrs - Wording - Feature badge (admin only)
-
由 Marcel Amirault 提交于
-
由 Cody West 提交于
Configuration examples were moved into their own section for the purpose of organizing and being able to link directly.
-
由 Stan Hu 提交于
Adding password in the Redis Sentinel config does not actually work because v3.2.x doesn't respond to the `AUTH` command. This came up in https://gitlab.com/gitlab-org/omnibus-gitlab/issues/4126.
-
- 20 2月, 2019 3 次提交
-
-
由 Marcel Amirault 提交于
-
由 Marcel Amirault 提交于
-
由 Joshua Lambert 提交于
-
- 18 2月, 2019 2 次提交
- 12 2月, 2019 4 次提交
-
-
由 Alessio Caiazza 提交于
-
由 Stan Hu 提交于
`queue_duration` is a useful metric that is currently in api_json.log but not in production_json.log. We should add it because it tells us how long the request sat in Workhorse before Unicorn processed it. Having this field enables the support team to better troubleshoot when delays began to happen.
-
由 Marcel Amirault 提交于
-
由 Tom Atkins 提交于
-
- 11 2月, 2019 3 次提交
-
-
由 Yorick Peterse 提交于
Instead of requiring one separate document for every version (which is created by release managers), we now use a single document for both Community Edition and Enterprise Edition. This allows developers to add guidelines right away, instead of release managers having to determine what to add. Version specific upgrading instructions are placed in a separate section. This prevents instructions from lingering around for many versions should a developer forget to remove them. This also ensures that all instructions are kept in a single place, instead of being spread across different documents. A minor downside is that CE and EE guidelines now live in the same document, which could cause merge conflicts. Since we are working towards a single codebase, this should only be an issue until we merge the codebases together; something we expect to do in the coming months. This commit also removes all old upgrading instructions, but these can still be accessed using Git branch specific URLs (included in the updating README).
-
由 Ben Bodenmiller 提交于
-
由 Abubakar Siddiq Ango 提交于
-
- 08 2月, 2019 3 次提交
- 07 2月, 2019 2 次提交
-
-
由 Ben Bodenmiller 提交于
-
由 Jan Provaznik 提交于
Cached markdown version is composed both from global and local markdown version. This allows admins to bump version locally when needed (e.g. when external URL is changed).
-
- 06 2月, 2019 1 次提交
-
-
由 Ben Kochie 提交于
Update the list of GitLab metrics to include the missing metric names.
-
- 05 2月, 2019 1 次提交
-
-
由 Nick Thomas 提交于
-
- 31 1月, 2019 1 次提交
-
-
由 Nick Thomas 提交于
-
- 30 1月, 2019 1 次提交
-
-
由 Evan Read 提交于
-
- 25 1月, 2019 1 次提交
-
-
由 Alexander Tanayno 提交于
-