1. 29 Jan, 2019 1 commit
  2. 15 Jan, 2019 2 commits
  3. 14 Jan, 2019 1 commit
  4. 19 Dec, 2018 3 commits
  5. 14 Dec, 2018 1 commit
  6. 11 Dec, 2018 1 commit
  7. 14 Nov, 2018 1 commit
    • Jan Provaznik's avatar
      Address specs failing in rails 4 · 134edbd7
      Jan Provaznik authored
      We want to run CI with rails 4 for a short-term (until we are sure that
      we will ship with rails 5). The problem is that rails 4 can not handle
      rails 5 schema.rb properly - specifically `t.index` directive can not
      handle multiple indexes on the same column.
      
      Because combination of rails 4 + rails 5 schema will be used
      only in CI for a short-term, we can just ignore these incompatibility
      failures. This patch adds `rails5` helper for specs.
      134edbd7
  8. 05 Oct, 2018 1 commit
  9. 10 Sep, 2018 1 commit
  10. 31 Aug, 2018 1 commit
  11. 16 Aug, 2018 2 commits
  12. 09 Jul, 2018 1 commit
  13. 06 Jul, 2018 1 commit
  14. 21 Jun, 2018 1 commit
  15. 14 Jun, 2018 1 commit
  16. 12 Jun, 2018 1 commit
  17. 05 Jun, 2018 1 commit
  18. 09 May, 2018 1 commit
  19. 04 May, 2018 1 commit
  20. 25 Apr, 2018 1 commit
  21. 23 Apr, 2018 1 commit
  22. 06 Apr, 2018 1 commit
  23. 03 Apr, 2018 1 commit
  24. 28 Mar, 2018 1 commit
    • Stan Hu's avatar
      Clean the test path after each spec run · d7dc9ad1
      Stan Hu authored
      FactoryBot's build_stubbed ignores the current database sequence of the
      projects table and starts at ID 1000. If more than 1000 projects are created
      during a test run, leftover repositories can cause spec failures. For example,
      a spec that expects an empty repository may fail since there may be existing
      content.
      
      Closes #5461
      d7dc9ad1
  25. 22 Mar, 2018 1 commit
  26. 01 Mar, 2018 1 commit
  27. 22 Feb, 2018 1 commit
  28. 16 Feb, 2018 1 commit
  29. 19 Jan, 2018 1 commit
  30. 15 Jan, 2018 1 commit
  31. 14 Dec, 2017 1 commit
  32. 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
  33. 30 Nov, 2017 1 commit
  34. 21 Nov, 2017 1 commit
  35. 02 Nov, 2017 2 commits