BigW Consortium Gitlab

  1. 11 Oct, 2016 1 commit
  2. 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.
  3. 07 Oct, 2016 2 commits
  4. 06 Oct, 2016 1 commit
  5. 05 Oct, 2016 1 commit
    • Refactor Gitlab::Identifier · 16ed9b61
      Yorick Peterse authored
      This refactors Gitlab::Identifier so it uses fewer queries and is
      actually tested. Queries are reduced by caching the output as well as
      using 1 query (instead of 2) to find a user using an SSH key.
  6. 04 Oct, 2016 1 commit
  7. 07 Sep, 2016 1 commit
    • Added cron to prune events older than 12 months. · e25b48ff
      Olaf Tomalka authored
      Since contribution calendar shows only 12 months of activity,
      events older than that time are not visible anywhere and can be
      safely pruned saving big amount of database storage.
      
      Fixes #21164
  8. 01 Sep, 2016 1 commit
  9. 19 Aug, 2016 2 commits
  10. 18 Aug, 2016 2 commits
  11. 12 Aug, 2016 1 commit
  12. 11 Aug, 2016 2 commits
    • 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
    • Pre-create all builds for Pipeline when a trigger is received · 39203f1a
      Kamil Trzcinski authored
      This change simplifies a Pipeline processing by introducing a special new status: created.
      This status is used for all builds that are created for a pipeline.
      We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped).
      This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled.
      This also allows us to visualise a full pipeline (with created builds).
      
      This also removes an after_touch used for updating a pipeline state parameters.
      Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
  13. 09 Aug, 2016 1 commit
  14. 07 Aug, 2016 1 commit
  15. 04 Aug, 2016 3 commits
  16. 26 Jul, 2016 1 commit
  17. 21 Jul, 2016 1 commit
  18. 13 Jul, 2016 1 commit
  19. 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
  20. 01 Jul, 2016 1 commit
  21. 30 Jun, 2016 1 commit
  22. 20 Jun, 2016 1 commit
  23. 17 Jun, 2016 1 commit
  24. 16 Jun, 2016 2 commits
  25. 15 Jun, 2016 1 commit
  26. 14 Jun, 2016 1 commit
  27. 13 Jun, 2016 5 commits
  28. 12 Jun, 2016 1 commit
  29. 03 Jun, 2016 1 commit