BigW Consortium Gitlab

  1. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
  2. 04 Oct, 2016 2 commits
    • Simplify Mentionable concern instance methods · 4ff345c4
      Paco Guzman authored
      We remove some arguments that are rarely used or 
      used just to simplify setups on specs.
      
      Modified Mentionable#create_new_cross_references method 
      we don’t need to calculate previous references to avoid the 
      duplication because we do that at database level when 
      creating references extracted from the current entity state.
      
      MergeRequests won’t create cross_references for commits that are included so we change a spec to use a different merge request to make references to commits to other branches
  3. 03 Oct, 2016 4 commits
  4. 01 Oct, 2016 2 commits
  5. 30 Sep, 2016 1 commit
  6. 29 Sep, 2016 1 commit
  7. 22 Sep, 2016 2 commits
  8. 20 Sep, 2016 3 commits
    • Implement (some) comments from @DouweM's review. · 71d4bf72
      Timothy Andrew authored
      - Move things common to `Issue` and `MergeRequest` into `Issuable`
      - Move more database-specific functions into `Gitlab::Database`
      - Indentation changes and other minor refactorings.
    • Implement review comments from @yorickpeterse · 8957293d
      Timothy Andrew authored
      1. Change multiple updates to a single `update_all`
      
      2. Use cascading deletes
      
      3. Extract an average function for the database median.
      
      4. Move database median to `lib/gitlab/database`
      
      5. Use `delete_all` instead of `destroy_all`
      
      6. Minor refactoring
    • Implement a database median strategy for MySQL. · 4ff8d5d2
      Timothy Andrew authored
      1. Dispatch between the two strategies automatically based on the
         current database type.
      
      2. The MySQL version needs to run multiple statements, so the
         `cycle_analytics` model is modified to support this.
  9. 19 Sep, 2016 2 commits
  10. 18 Sep, 2016 1 commit
  11. 17 Sep, 2016 1 commit
    • Move cycle analytics calculations to SQL. · 7d69ff3d
      Timothy Andrew authored
      1. Use Arel for composable queries.
      2. For a project with ~10k issues, the page loads in around 600ms.
         Previously, a project with ~5k issues would have a ~20s page load
         time.
  12. 14 Sep, 2016 1 commit
  13. 13 Sep, 2016 1 commit
  14. 12 Sep, 2016 1 commit
  15. 01 Sep, 2016 1 commit
  16. 31 Aug, 2016 1 commit
  17. 30 Aug, 2016 2 commits
  18. 29 Aug, 2016 1 commit
  19. 28 Aug, 2016 1 commit
  20. 25 Aug, 2016 1 commit
  21. 23 Aug, 2016 1 commit
  22. 22 Aug, 2016 1 commit
  23. 19 Aug, 2016 3 commits
  24. 18 Aug, 2016 1 commit
  25. 16 Aug, 2016 1 commit
    • Backport changes from gitlab-org/gitlab-ee!581 to CE. · e805a647
      Timothy Andrew authored
      !581 has a lot of changes that would cause merge conflicts if not
      properly backported to CE. This commit/MR serves as a better
      foundation for gitlab-org/gitlab-ee!581.
      
      = Changes =
      
      1. Move from `has_one {merge,push}_access_level` to `has_many`, with the
         `length` of the association limited to `1`. This is _effectively_ a
         `has_one` association, but should cause less conflicts with EE, which
         is set to `has_many`. This has a number of related changes in the
         views, specs, and factories.
      
      2. Make `gon` variable loading more consistent (with EE!581) in the
         `ProtectedBranchesController`. Also use `::` to prefix the
         `ProtectedBranches` services, because this is required in EE.
      
      3. Extract a `ProtectedBranchAccess` concern from the two access level
         models. This concern only has a single `humanize` method here, but
         will have more methods in EE.
      
      4. Add `form_errors` to the protected branches creation form. This is
         not strictly required for EE compatibility, but was an oversight
         nonetheless.
  26. 15 Aug, 2016 3 commits