BigW Consortium Gitlab

  1. 07 Dec, 2017 1 commit
  2. 05 Dec, 2017 1 commit
    • Create merge request from email · 8cce7073
      Jan Provaznik authored
      * 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
  3. 04 Dec, 2017 2 commits
  4. 01 Dec, 2017 2 commits
  5. 28 Nov, 2017 4 commits
  6. 24 Nov, 2017 1 commit
  7. 09 Nov, 2017 2 commits
  8. 07 Nov, 2017 1 commit
    • Rewrite the GitHub importer from scratch · 4dfe26cd
      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
      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.
  9. 06 Nov, 2017 2 commits
  10. 03 Nov, 2017 1 commit
  11. 31 Oct, 2017 2 commits
  12. 27 Oct, 2017 1 commit
  13. 13 Oct, 2017 1 commit
  14. 11 Oct, 2017 1 commit
  15. 10 Oct, 2017 1 commit
  16. 09 Oct, 2017 1 commit
  17. 07 Oct, 2017 2 commits
  18. 06 Oct, 2017 1 commit
    • Create idea of read-only database · d1366971
      Toon Claes authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      
      Closes gitlab-org/gitlab-ce#37534.
  19. 05 Oct, 2017 3 commits
  20. 04 Oct, 2017 1 commit
  21. 02 Oct, 2017 1 commit
    • Fix gitlab-rake gitlab:import:repos task · bac29160
      Stan Hu authored
      Because of a change in GitLab 9.5.4 to prevent users from assuming control of
      a repository already on disk, the import task broke. Imports would fail with
      the message, "There is already a repository with that name on disk".
      
      This change skips the validation when the import is done from the
      command-line.
      
      Closes #37682
  22. 29 Sep, 2017 1 commit
  23. 28 Sep, 2017 1 commit
  24. 20 Sep, 2017 1 commit
  25. 14 Sep, 2017 1 commit
  26. 07 Sep, 2017 1 commit
  27. 06 Sep, 2017 1 commit
  28. 05 Sep, 2017 1 commit
    • Optimize SQL queries used in Groups::GroupMembersController#create · 66cfb901
      Rubén Dávila authored
      The following optimizations were performed:
      
      - Add new association to GroupMember and ProjectMember
      
        This new association will allow us to check if a user is a member of a
        Project or Group through a single query instead of two.
      
      - Optimize retrieving of Members when adding multiple Users
  29. 04 Sep, 2017 1 commit