1. 07 Feb, 2019 1 commit
  2. 06 Feb, 2019 1 commit
  3. 05 Feb, 2019 1 commit
    • Nick Thomas's avatar
      Fix a conflict in GITALY_SERVER_VERSION · d18cd4ad
      Nick Thomas authored
      GitLab.com master now points at Gitaly v1.17.0. Dev master pointed at
      1.14.1 due to a recent security release. That fix is present in 1.17.0
      so it is safe to take the .com side here.
      d18cd4ad
  4. 01 Feb, 2019 1 commit
  5. 31 Jan, 2019 1 commit
  6. 24 Jan, 2019 1 commit
  7. 22 Jan, 2019 1 commit
  8. 16 Jan, 2019 1 commit
  9. 21 Dec, 2018 1 commit
  10. 19 Dec, 2018 1 commit
  11. 17 Dec, 2018 1 commit
  12. 06 Dec, 2018 1 commit
  13. 27 Nov, 2018 1 commit
  14. 26 Nov, 2018 1 commit
  15. 23 Nov, 2018 1 commit
  16. 19 Nov, 2018 1 commit
  17. 14 Nov, 2018 1 commit
  18. 07 Nov, 2018 1 commit
  19. 05 Nov, 2018 1 commit
  20. 23 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Bump Gitaly to v0.126.0 · c40b5aaa
      Zeger-Jan van de Weg authored
      This will allow changes in Gitaly that will make it fail when running
      rspec, to make it to GitLab.
      
      Else Gitaly won't start as it can't reach the broken storage directory.
      c40b5aaa
  21. 15 Oct, 2018 1 commit
  22. 06 Oct, 2018 1 commit
  23. 04 Oct, 2018 1 commit
  24. 01 Oct, 2018 1 commit
  25. 27 Sep, 2018 1 commit
  26. 13 Sep, 2018 1 commit
  27. 07 Sep, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Port cleanup tasks to use Gitaly · 3aedccb1
      Zeger-Jan van de Weg authored
      Rake tasks cleaning up the Git storage were still using direct disk
      access, which won't work if these aren't attached. To mitigate a
      migration issue was created.
      
      To port gitlab:cleanup:dirs, and gitlab:cleanup:repos, a new RPC was
      required, ListDirectories. This was implemented in Gitaly, through
      gitlab-org/gitaly!868.
      
      To be able to use the new RPC the Gitaly server was bumped to v0.120.
      
      This is an RPC that will not use feature gates, as this doesn't scale on
      .com so there is no way to test it at scale. Futhermore, we _know_ it
      doesn't scale, but this might be a useful task for smaller instances.
      
      Lastly, the tests are slightly updated to also work when the disk isn't
      attached. Eventhough this is not planned, it was very little effort and
      thus I applied the boy scout rule.
      
      Closes gitlab-org/gitaly#954
      Closes gitlab-org/gitlab-ce#40529
      3aedccb1
  28. 06 Sep, 2018 1 commit
  29. 17 Aug, 2018 2 commits
  30. 07 Aug, 2018 1 commit
  31. 06 Aug, 2018 1 commit
  32. 03 Aug, 2018 1 commit
  33. 31 Jul, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Bump Gitaly version · 4702c9f7
      Zeger-Jan van de Weg authored
      This branch includes changes that removes a rake taks that cleans up
      config.lock files.
      
      This change bumps Gitaly so it happens automatically so users don't have
      to bother.
      4702c9f7
  34. 18 Jul, 2018 1 commit
  35. 11 Jul, 2018 1 commit
  36. 06 Jul, 2018 1 commit
  37. 03 Jul, 2018 1 commit
  38. 27 Jun, 2018 2 commits
    • Jacob Vosmaer's avatar
      Migrate storage nesting check to Gitaly · 1142e2c3
      Jacob Vosmaer authored
      1142e2c3
    • Zeger-Jan van de Weg's avatar
      Gitaly metrics check for read/writeability · 65840591
      Zeger-Jan van de Weg authored
      Prior to this change, health checks checked for writeability of the NFS
      shards. Given we're moving away from that, this patch extends the checks
      for Gitaly to check for read and writeability.
      
      Potentially some dashboards will break, as over time these metrics will
      no longer appear as Prometheus doesn't get the data anymore.
      Observability in the circuit breaker will be reduced, but its not
      expected to be turned on and the circuit breaker is being removed soon
      too.
      
      Closes gitlab-org/gitaly#1218
      65840591