1. 05 3月, 2016 1 次提交
  2. 03 3月, 2016 1 次提交
  3. 26 2月, 2016 1 次提交
    • Y
      Flush repository caches before renaming projects · 1dfef90a
      Yorick Peterse 提交于
      This ensures that if a project is later re-created using the old path it
      doesn't end up re-using the old cache. This also ensures we don't keep
      the cache around until its expired by Redis itself.
      
      Fixes gitlab-org/gitlab-ce#13790
      1dfef90a
  4. 25 2月, 2016 2 次提交
  5. 23 2月, 2016 1 次提交
  6. 17 2月, 2016 1 次提交
  7. 16 2月, 2016 1 次提交
  8. 12 2月, 2016 1 次提交
    • K
      Add new data to project in push, issue, merge-request and note webhooks data · b123171d
      Kirill Zaitsev 提交于
      - Add `avatar_url`, `description`, `git_ssh_url`, `git_http_url`,
        `path_with_namespace` and `default_branch` in `project` in push, issue,
        merge-request and note webhooks data
      - Deprecate the `ssh_url` in favor of `git_ssh_url` and `http_url` in
        favor of `git_http_url` in `project` for push, issue, merge-request and
        note webhooks data
      - Deprecate the `repository` key in push, issue, merge-request and
        note webhooks data, use `project` instead
      b123171d
  9. 08 2月, 2016 1 次提交
    • Y
      Cache various Repository Git operations · 9a99d8e4
      Yorick Peterse 提交于
      This caches the output of the following methods:
      
      * Repository#empty?
      * Repository#has_visible_content?
      * Repository#root_ref
      
      The cache for Repository#has_visible_content? is flushed whenever a
      commit is pushed to a new branch or an existing branch is removed.
      The cache for Repository#root_ref is only flushed whenever a user
      changes the default branch of a project. The cache for Repository#empty?
      is never explicitly flushed as there's no need for it.
      9a99d8e4
  10. 05 2月, 2016 2 次提交
  11. 03 2月, 2016 3 次提交
  12. 29 1月, 2016 1 次提交
  13. 28 1月, 2016 2 次提交
  14. 27 1月, 2016 1 次提交
    • Y
      Use Atom update times of the first event · de7c9c7a
      Yorick Peterse 提交于
      By simply loading the first event from the already sorted set we save
      ourselves extra (slow) queries just to get the latest update timestamp.
      This removes the need for Event.latest_update_time and significantly
      reduces the time needed to build an Atom feed.
      
      Fixes gitlab-org/gitlab-ce#12415
      de7c9c7a
  15. 26 1月, 2016 1 次提交
  16. 23 1月, 2016 1 次提交
  17. 22 1月, 2016 1 次提交
  18. 21 1月, 2016 1 次提交
  19. 19 1月, 2016 3 次提交
    • J
      Add specs. Adjust filter. · ae6080c7
      Josh Frye 提交于
      ae6080c7
    • J
      Change 'public' flag to more robust 'visibility' query. · 11797df1
      Josh Frye 提交于
      11797df1
    • Y
      Greatly improve external_issue_tracker performance · b4ee6f57
      Yorick Peterse 提交于
      This greatly improves the performance of Project#external_issue_tracker
      by moving most of the fields queried in Ruby to the database and letting
      the database handle all logic. Prior to this change the process of
      finding an external issue tracker was along the lines of the following:
      
      1. Load all project services into memory.
      2. Reduce the list to only services where "issue_tracker?" returns true
      3. Reduce the list from step 2 to service where "default?" returns false
      4. Find the first service where "activated?" returns true
      
      This has to two big problems:
      
      1. Loading all services into memory only to reduce the list down to a
         single item later on is a waste of memory (and slow timing wise).
      2. Calling Array#select followed by Array#reject followed by Array#find
         allocates extra objects when this really isn't needed.
      
      To work around this the following service fields have been moved to the
      database (instead of being hardcoded):
      
      * category
      * default
      
      This in turn means we can get the external issue tracker using the
      following query:
      
          SELECT *
          FROM services
          WHERE active IS TRUE
          AND default IS FALSE
          AND category = 'issue_tracker'
          AND project_id = XXX
          LIMIT 1
      
      This coupled with memoizing the result (just as before this commit)
      greatly reduces the time it takes for Project#external_issue_tracker to
      complete. The exact reduction depends on one's environment, but locally
      the execution time is reduced from roughly 230 ms to only 2 ms (= a
      reduction of almost 180x).
      
      Fixes gitlab-org/gitlab-ce#10771
      b4ee6f57
  20. 14 1月, 2016 1 次提交
  21. 11 1月, 2016 2 次提交
  22. 06 1月, 2016 1 次提交
  23. 04 1月, 2016 1 次提交
  24. 30 12月, 2015 1 次提交
  25. 19 12月, 2015 1 次提交
  26. 17 12月, 2015 1 次提交
  27. 15 12月, 2015 1 次提交
  28. 12 12月, 2015 5 次提交