BigW Consortium Gitlab

  1. 10 Oct, 2016 1 commit
    • Precalculate trending projects · 237c8f66
      Yorick Peterse authored
      This commit introduces a Sidekiq worker that precalculates the list of
      trending projects on a daily basis. The resulting set is stored in a
      database table that is then queried by Project.trending.
      
      This setup means that Unicorn workers no longer _may_ have to calculate
      the list of trending projects. Furthermore it supports filtering without
      any complex caching mechanisms.
      
      The data in the "trending_projects" table is inserted in the same order
      as the project ranking. This means that getting the projects in the
      correct order is simply a matter of:
      
          SELECT projects.*
          FROM projects
          INNER JOIN trending_projects ON trending_projects.project_id = projects.id
          ORDER BY trending_projects.id ASC;
      
      Such a query will only take a few milliseconds at most (as measured on
      GitLab.com), opposed to a few seconds for the query used for calculating
      the project ranks.
      
      The migration in this commit does not require downtime and takes care of
      populating an initial list of trending projects.
  2. 07 Oct, 2016 3 commits
  3. 06 Oct, 2016 1 commit
  4. 04 Oct, 2016 4 commits
  5. 03 Oct, 2016 1 commit
  6. 07 Sep, 2016 3 commits
  7. 24 Aug, 2016 1 commit
  8. 19 Aug, 2016 1 commit
  9. 18 Aug, 2016 1 commit
  10. 17 Aug, 2016 1 commit
    • Tracking of custom events · d345591f
      Yorick Peterse authored
      GitLab Performance Monitoring is now able to track custom events not
      directly related to application performance. These events include the
      number of tags pushed, repositories created, builds registered, etc.
      
      The use of these events is to get a better overview of how a GitLab
      instance is used and how that may affect performance. For example, a
      large number of Git pushes may have a negative impact on the underlying
      storage engine.
      
      Events are stored in the "events" measurement and are not prefixed with
      "rails_" or "sidekiq_", this makes it easier to query events with the
      same name triggered from different parts of the application. All events
      being stored in the same measurement also makes it easier to downsample
      data.
      
      Currently the following events are tracked:
      
      * Creating repositories
      * Removing repositories
      * Changing the default branch of a repository
      * Pushing a new tag
      * Removing an existing tag
      * Pushing a commit (along with the branch being pushed to)
      * Pushing a new branch
      * Removing an existing branch
      * Importing a repository (along with the URL we're importing)
      * Forking a repository (along with the source/target path)
      * CI builds registered (and when no build could be found)
      * CI builds being updated
      * Rails and Sidekiq exceptions
      
      Fixes gitlab-org/gitlab-ce#13720
  11. 11 Aug, 2016 1 commit
    • Fix bug where destroying a namespace would not always destroy projects · cb8a425b
      Stan Hu authored
      There is a race condition in DestroyGroupService now that projects are deleted asynchronously:
      
      1. User attempts to delete group
      2. DestroyGroupService iterates through all projects and schedules a Sidekiq job to delete each Project
      3. DestroyGroupService destroys the Group, leaving all its projects without a namespace
      4. Projects::DestroyService runs later but the can?(current_user,
         :remove_project) is `false` because the user no longer has permission to
         destroy projects with no namespace.
      5. This leaves the project in pending_delete state with no namespace/group.
      
      Projects without a namespace or group also adds another problem: it's not possible to destroy the container
      registry tags, since container_registry_path_with_namespace is the wrong value.
      
      The fix is to destroy the group asynchronously and to run execute directly on Projects::DestroyService.
      
      Closes #17893
  12. 09 Aug, 2016 1 commit
  13. 07 Aug, 2016 1 commit
  14. 05 Aug, 2016 1 commit
  15. 04 Aug, 2016 4 commits
  16. 03 Aug, 2016 4 commits
  17. 26 Jul, 2016 2 commits
  18. 21 Jul, 2016 2 commits
  19. 18 Jul, 2016 1 commit
  20. 13 Jul, 2016 1 commit
  21. 12 Jul, 2016 1 commit
    • Expire the branch cache after `git gc` runs · 3dc6bf2b
      Stan Hu authored
      Due to a stale NFS cache, it's possible that a branch lookup fails
      while `git gc` is running and causes missing branches in merge requests.
      
      Possible workaround for #15392
  22. 06 Jul, 2016 1 commit
  23. 30 Jun, 2016 1 commit
  24. 16 Jun, 2016 2 commits