1. 19 Jan, 2018 1 commit
  2. 15 Jan, 2018 1 commit
  3. 14 Dec, 2017 1 commit
  4. 08 Dec, 2017 1 commit
    • Bob Van Landuyt's avatar
      Move the circuitbreaker check out in a separate process · f1ae1e39
      Bob Van Landuyt authored
      Moving the check out of the general requests, makes sure we don't have
      any slowdown in the regular requests.
      
      To keep the process performing this checks small, the check is still
      performed inside a unicorn. But that is called from a process running
      on the same server.
      
      Because the checks are now done outside normal request, we can have a
      simpler failure strategy:
      
      The check is now performed in the background every
      `circuitbreaker_check_interval`. Failures are logged in redis. The
      failures are reset when the check succeeds. Per check we will try
      `circuitbreaker_access_retries` times within
      `circuitbreaker_storage_timeout` seconds.
      
      When the number of failures exceeds
      `circuitbreaker_failure_count_threshold`, we will block access to the
      storage.
      
      After `failure_reset_time` of no checks, we will clear the stored
      failures. This could happen when the process that performs the checks
      is not running.
      f1ae1e39
  5. 30 Nov, 2017 1 commit
  6. 21 Nov, 2017 1 commit
  7. 02 Nov, 2017 2 commits
  8. 16 Oct, 2017 1 commit
  9. 04 Oct, 2017 1 commit
  10. 03 Oct, 2017 1 commit
  11. 22 Sep, 2017 1 commit
  12. 14 Sep, 2017 1 commit
  13. 22 Aug, 2017 1 commit
  14. 17 Aug, 2017 1 commit
    • Grzegorz Bizon's avatar
      Migrate down before each migration unit test · 56d24bcf
      Grzegorz Bizon authored
      `migrate!` helper triggers a migration that is under the test, so we
      need to revert it before each subsequent example. This means that we
      need to place it in `before(:each, :migration)` hook.
      
      We still want to migrate everything up *after* each *context*, so in
      otherwords we need to place migrate up helper in `before(:context,
      :migration)`.
      56d24bcf
  15. 16 Aug, 2017 2 commits
  16. 11 Aug, 2017 3 commits
  17. 07 Aug, 2017 1 commit
    • Lin Jen-Shin's avatar
      Reset only migration models · 4d7c072d
      Lin Jen-Shin authored
      So that we could make sure migration tests could run even if
      geo is not setup in EE.
      
      This is because we have a model like this:
      
      ``` ruby
      class Geo::BaseRegistry < ActiveRecord::Base
        def self.connection
          raise 'Geo secondary database is not configured' unless Gitlab::Geo.geo_database_configured?
      
          super
        end
      end
      ```
      4d7c072d
  18. 02 Aug, 2017 1 commit
  19. 31 Jul, 2017 1 commit
  20. 28 Jul, 2017 1 commit
  21. 27 Jul, 2017 3 commits
  22. 24 Jul, 2017 1 commit
  23. 19 Jul, 2017 1 commit
  24. 13 Jul, 2017 1 commit
    • Bob Van Landuyt's avatar
      Enable all feature flags by default in specs · 3ee48e42
      Bob Van Landuyt authored
      Otherwise some features would go untested in non-specific contexts
      
      I did need to disable the
      `gitlab_git_diff_size_limit_increase`-feature in some specs since we
      depend on diffs being expandable while the file we are testing on is
      smaller than the increased limit.
      3ee48e42
  25. 12 Jul, 2017 1 commit
  26. 11 Jul, 2017 1 commit
  27. 07 Jul, 2017 1 commit
  28. 05 Jul, 2017 1 commit
  29. 19 Jun, 2017 1 commit
  30. 15 Jun, 2017 1 commit
  31. 13 Jun, 2017 1 commit
  32. 12 Jun, 2017 1 commit
  33. 09 Jun, 2017 1 commit
  34. 05 Jun, 2017 1 commit