BigW Consortium Gitlab

  1. 26 Jun, 2017 1 commit
  2. 16 Jun, 2017 1 commit
    • Add table for files in merge request diffs · 9a73b634
      Sean McGivern authored
      This adds an ID-less table containing one row per file, per merge request
      diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised
      currently, with the advantage that we can easily query the attributes of this
      new table.
      
      It does not migrate existing data, so we have fallback code when the legacy
      st_diffs column is present instead. For a merge request diff to be valid, it
      should have at most one of:
      
      * Rows in this new table, with the correct merge_request_diff_id.
      * A non-NULL st_diffs column.
      
      It may have neither, if the diff is empty.
  3. 11 Apr, 2017 1 commit
  4. 17 Mar, 2017 1 commit
    • Added Gitlab::Database.config · 9a20ff1c
      Yorick Peterse authored
      This returns the ActiveRecord configuration for the current environment.
      
      While CE doesn't use this very often, EE will use it in a few places for
      the database load balancing code. I'm adding this to CE so we don't end
      up with merge conflicts in this file.
  5. 02 Mar, 2017 1 commit
  6. 22 Feb, 2017 1 commit
    • Allow setting of a custom connection pool host · cf521c95
      Yorick Peterse authored
      This allows you to set a custom host when calling
      Gitlab::Database.create_connection_pool. This is necessary for load
      balancing as in this case we want to inherit all settings except for the
      hostname.
  7. 14 Feb, 2017 1 commit
  8. 13 Feb, 2017 2 commits
  9. 06 Feb, 2017 1 commit
  10. 25 Nov, 2016 1 commit
    • Refresh project authorizations using a Redis lease · 92b2c74c
      Yorick Peterse authored
      When I proposed using serializable transactions I was hoping we would be
      able to refresh data of individual users concurrently. Unfortunately
      upon closer inspection it was revealed this was not the case. This could
      result in a lot of queries failing due to serialization errors,
      overloading the database in the process (given enough workers trying to
      update the target table).
      
      To work around this we're now using a Redis lease that is cancelled upon
      completion. This ensures we can update the data of different users
      concurrently without overloading the database.
      
      The code will try to obtain the lease until it succeeds, waiting at
      least 1 second between retries. This is necessary as we may otherwise
      end up _not_ updating the data which is not an option.
  11. 18 Nov, 2016 1 commit
  12. 19 Jul, 2016 1 commit
  13. 18 Jun, 2016 1 commit
  14. 16 Jun, 2016 2 commits
  15. 15 Jun, 2016 1 commit
  16. 06 Jun, 2016 1 commit
  17. 03 Jun, 2016 2 commits
  18. 11 May, 2016 1 commit
  19. 15 Feb, 2016 1 commit
  20. 02 Feb, 2016 1 commit
  21. 10 Dec, 2015 1 commit
  22. 22 Oct, 2015 1 commit
  23. 07 Oct, 2015 1 commit