1. 04 May, 2018 1 commit
  2. 07 Mar, 2018 1 commit
  3. 28 Feb, 2018 1 commit
  4. 09 Feb, 2018 2 commits
  5. 01 Feb, 2018 1 commit
    • Yorick Peterse's avatar
      Track and act upon the number of executed queries · 9627f5de5a69
      Yorick Peterse authored
      This ensures that we have more visibility in the number of SQL queries
      that are executed in web requests. The current threshold is hardcoded to
      100 as we will rarely (maybe once or twice) change it.
      In production and development we use Sentry if enabled, in the test
      environment we raise an error. This feature is also only enabled in
      production/staging when running on GitLab.com as it's not very useful to
      other users.
  6. 16 Nov, 2017 1 commit
  7. 07 Nov, 2017 1 commit
    • Yorick Peterse's avatar
      Rewrite the GitHub importer from scratch · 86c05c535691
      Yorick Peterse authored
      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
      == 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.
  8. 14 Aug, 2017 1 commit
  9. 09 Aug, 2017 1 commit
  10. 08 Aug, 2017 1 commit
  11. 07 Aug, 2017 1 commit
  12. 28 Jul, 2017 1 commit
    • Z.J. van de Weg's avatar
      Allow projects to be started from a template · e370c475ec76
      Z.J. van de Weg authored
      Started implementation for the first iteration of
      gitlab-org/gitlab-ce#32420. This will allow users to select a template
      to start with, instead of an empty repository in the project just
      Internally this is basically a small extension of the ImportExport
      GitLab projects we already support. We just import a certain import
      tar archive. This commits includes the first one: Ruby on Rails. In the
      future more will be added.
  13. 05 Apr, 2017 1 commit
  14. 30 Mar, 2017 1 commit
  15. 21 Mar, 2017 1 commit
  16. 23 Feb, 2017 4 commits
  17. 21 Feb, 2017 1 commit
  18. 19 Dec, 2016 5 commits
  19. 15 Dec, 2016 1 commit
  20. 09 Dec, 2016 1 commit
  21. 07 Dec, 2016 1 commit
  22. 22 Nov, 2016 5 commits
  23. 24 Oct, 2016 1 commit
  24. 03 Oct, 2016 1 commit
  25. 20 Sep, 2016 1 commit
  26. 31 Aug, 2016 2 commits
  27. 25 Aug, 2016 1 commit