- 08 12月, 2017 1 次提交
-
-
由 Achilleas Pipinellis 提交于
-
- 07 12月, 2017 3 次提交
-
-
由 Marcia Ramos 提交于
-
由 Shinya Maeda 提交于
-
由 Takuya Noguchi 提交于
-
- 05 12月, 2017 2 次提交
-
-
由 Jan Provaznik 提交于
* new merge request can be created by sending an email to the specific email address (similar to creating issues by email) * for the first iteration, source branch must be specified in the mail subject, other merge request parameters can not be set yet * user should enable "Receive notifications about your own activity" in user settings to receive a notification about created merge request Part of #32878
-
由 Marcia Ramos 提交于
- Assign issues and MRs - Label issues and MRs - Reorder a couple of items in the table to go from unchecked to checked - Add/remove spaces so that the dividers stay in the same column in the file
-
- 02 12月, 2017 2 次提交
-
-
由 Koichiro Mikami 提交于
-
由 Achilleas Pipinellis 提交于
-
- 29 11月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
The st_commits and st_diffs columns on merge_request_diffs historically held the YAML-serialised data for a merge request diff, in a variety of formats. Since 9.5, these have been migrated in the background to two new tables: merge_request_diff_commits and merge_request_diff_files. That has the advantage that we can actually query the data (for instance, to find out how many commits we've stored), and that it can't be in a variety of formats, but must match the new schema. This is the final step of that journey, where we drop those columns and remove all references to them. This is a breaking change to the importer, because we can no longer import diffs created in the old format, and we cannot guarantee the export will be in the new format unless it was generated after this commit.
-
- 25 11月, 2017 2 次提交
-
-
由 David Muckle 提交于
-
由 Christiaan Van den Poel 提交于
-
- 23 11月, 2017 1 次提交
-
-
由 Achilleas Pipinellis 提交于
-
- 22 11月, 2017 1 次提交
-
-
- 21 11月, 2017 1 次提交
-
-
由 Victor Wu 提交于
-
- 20 11月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 19 11月, 2017 1 次提交
-
-
由 Elan Ruusamäe 提交于
-
- 18 11月, 2017 1 次提交
-
-
由 Stan Hu 提交于
This was causing a docs lint failure in https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/40901316.
-
- 17 11月, 2017 5 次提交
-
-
由 Achilleas Pipinellis 提交于
-
由 Achilleas Pipinellis 提交于
-
由 Achilleas Pipinellis 提交于
-
由 Achilleas Pipinellis 提交于
-
由 Achilleas Pipinellis 提交于
-
- 16 11月, 2017 1 次提交
-
-
由 James Ramsay 提交于
The option to choose readme only as a users default project view was restored in !14900
-
- 14 11月, 2017 1 次提交
-
-
由 Chế Tiệp Chân Khoa 提交于
-
- 13 11月, 2017 1 次提交
-
-
由 Joshua Lambert 提交于
-
- 11 11月, 2017 1 次提交
-
-
由 Mark Fletcher 提交于
-
- 08 11月, 2017 2 次提交
-
-
由 Yorick Peterse 提交于
Prior to this MR there were two GitHub related importers: * Github::Import: the main importer used for GitHub projects * Gitlab::GithubImport: importer that's somewhat confusingly used for importing Gitea projects (apparently they have a compatible API) This MR renames the Gitea importer to Gitlab::LegacyGithubImport and introduces a new GitHub importer in the Gitlab::GithubImport namespace. This new GitHub importer uses Sidekiq for importing multiple resources in parallel, though it also has the ability to import data sequentially should this be necessary. The new code is spread across the following directories: * lib/gitlab/github_import: this directory contains most of the importer code such as the classes used for importing resources. * app/workers/gitlab/github_import: this directory contains the Sidekiq workers, most of which simply use the code from the directory above. * app/workers/concerns/gitlab/github_import: this directory provides a few modules that are included in every GitHub importer worker. == Stages The import work is divided into separate stages, with each stage importing a specific set of data. Stages will schedule the work that needs to be performed, followed by scheduling a job for the "AdvanceStageWorker" worker. This worker will periodically check if all work is completed and schedule the next stage if this is the case. If work is not yet completed this worker will reschedule itself. Using this approach we don't have to block threads by calling `sleep()`, as doing so for large projects could block the thread from doing any work for many hours. == Retrying Work Workers will reschedule themselves whenever necessary. For example, hitting the GitHub API's rate limit will result in jobs rescheduling themselves. These jobs are not processed until the rate limit has been reset. == User Lookups Part of the importing process involves looking up user details in the GitHub API so we can map them to GitLab users. The old importer used an in-memory cache, but this obviously doesn't work when the work is spread across different threads. The new importer uses a Redis cache and makes sure we only perform API/database calls if absolutely necessary. Frequently used keys are refreshed, and lookup misses are also cached; removing the need for performing API/database calls if we know we don't have the data we're looking for. == Performance & Models The new importer in various places uses raw INSERT statements (as generated by `Gitlab::Database.bulk_insert`) instead of using Rails models. This allows us to bypass any validations and callbacks, drastically reducing the number of SQL queries and Gitaly RPC calls necessary to import projects. To ensure the code produces valid data the corresponding tests check if the produced rows are valid according to the model validation rules.
-
由 Chenjerai Katanda 提交于
-
- 07 11月, 2017 4 次提交
-
-
由 Victor Wu 提交于
-
由 Victor Wu 提交于
-
由 Eric Eastwood 提交于
-
由 Shinya Maeda 提交于
-
- 04 11月, 2017 1 次提交
-
-
由 Eric Eastwood 提交于
-
- 03 11月, 2017 2 次提交
-
-
由 Pawel Chojnacki 提交于
-
由 Pawel Chojnacki 提交于
-
- 02 11月, 2017 4 次提交
-
-
由 Eric Eastwood 提交于
Prompted to add this note from https://gitlab.com/gitlab-org/gitlab-ce/issues/34102#note_45522526
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Alexander Randa 提交于
-