This instance will be upgraded to Heptapod 0.31.0rc on 2022-05-19 at 11:00 UTC+2 (a few minutes of down time)

  1. 27 Nov, 2018 1 commit
  2. 11 Sep, 2018 1 commit
  3. 06 Sep, 2018 1 commit
  4. 29 Aug, 2018 1 commit
  5. 30 Jul, 2018 1 commit
  6. 22 Jul, 2018 1 commit
  7. 27 Jun, 2018 5 commits
  8. 21 Jun, 2018 1 commit
    • Yorick Peterse's avatar
      Don't expose project names in various counters · 76e4045a747c
      Yorick Peterse authored
      Various counters would expose either project names, or full project
      paths (e.g. "gitlab-org/gitlab-ce"). This commit changes various places
      where we use "add_event" so we no longer expose (potentially) private
  9. 25 Apr, 2018 1 commit
    • Sean McGivern's avatar
      Move NotificationService calls to Sidekiq · d2c64edc98bd
      Sean McGivern authored
      The NotificationService has to do quite a lot of work to calculate the
      recipients for an email. Where possible, we should try to avoid doing this in an
      HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to
      schedule those emails immediately.
      This commit creates a generic Sidekiq worker that uses Global ID to serialise
      and deserialise its arguments, then forwards them to the NotificationService.
      The NotificationService gains an `#async` method, so you can replace:
          notification_service.new_issue(issue, current_user)
          notification_service.async.new_issue(issue, current_user)
      And have everything else work as normal, except that calculating the recipients
      will be done by Sidekiq, which will then schedule further Sidekiq jobs to send
      each email.
  10. 30 Mar, 2018 1 commit
    • Sean McGivern's avatar
      Send emails for issues due tomorrow · eed80ce5926d
      Sean McGivern authored
      Also, refactor the mail sending slightly: instead of one worker sending all
      emails, create a worker per project with issues due, which will send all emails
      for that project.
  11. 06 Mar, 2018 3 commits
  12. 05 Mar, 2018 1 commit
  13. 01 Mar, 2018 1 commit
  14. 26 Feb, 2018 2 commits
  15. 11 Jan, 2018 1 commit
    • Stan Hu's avatar
      Remove warning noise in ProjectImportOptions · fffa9c38b017
      Stan Hu authored
      Squlches these warnings:
      /opt/gitlab/embedded/service/gitlab-rails/app/workers/concerns/project_import_options.rb:5: warning: already initialized constant ProjectImportOptions::IMPORT_RETRY_COUNT
      /opt/gitlab/embedded/service/gitlab-rails/app/workers/concerns/project_import_options.rb:5: warning: previous definition of IMPORT_RETRY_COUNT was here
  16. 15 Dec, 2017 1 commit
  17. 13 Dec, 2017 1 commit
  18. 12 Dec, 2017 1 commit
  19. 05 Dec, 2017 2 commits
  20. 22 Nov, 2017 1 commit
  21. 17 Nov, 2017 1 commit
  22. 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.
  23. 03 Nov, 2017 1 commit
  24. 02 Nov, 2017 3 commits
  25. 10 Oct, 2017 1 commit
  26. 03 Oct, 2017 2 commits
  27. 18 Sep, 2017 1 commit
  28. 25 Aug, 2017 2 commits