1. 26 Feb, 2016 1 commit
    • Zeger-Jan van de Weg's avatar
      Branded login page also in CE · 9a2869ab
      Zeger-Jan van de Weg authored
      The only major difference with the EE version is the change from a light and dark logo to only a header logo
      The dark logo wasn't used anyway, so it seemed to make sense to me to rename the field to the actual function of it
  2. 20 Feb, 2016 3 commits
  3. 19 Feb, 2016 3 commits
  4. 17 Feb, 2016 1 commit
    • Tap's avatar
      Label description and Label row · 2e81b155
      Tap authored
      - Add label description
      - Show label row when filtering issues or merge requests by label
  5. 09 Feb, 2016 2 commits
  6. 04 Feb, 2016 1 commit
  7. 02 Feb, 2016 3 commits
  8. 29 Jan, 2016 3 commits
  9. 28 Jan, 2016 1 commit
  10. 20 Jan, 2016 2 commits
  11. 19 Jan, 2016 2 commits
    • Douwe Maan's avatar
    • Yorick Peterse's avatar
      Greatly improve external_issue_tracker performance · b4ee6f57
      Yorick Peterse authored
      This greatly improves the performance of Project#external_issue_tracker
      by moving most of the fields queried in Ruby to the database and letting
      the database handle all logic. Prior to this change the process of
      finding an external issue tracker was along the lines of the following:
      1. Load all project services into memory.
      2. Reduce the list to only services where "issue_tracker?" returns true
      3. Reduce the list from step 2 to service where "default?" returns false
      4. Find the first service where "activated?" returns true
      This has to two big problems:
      1. Loading all services into memory only to reduce the list down to a
         single item later on is a waste of memory (and slow timing wise).
      2. Calling Array#select followed by Array#reject followed by Array#find
         allocates extra objects when this really isn't needed.
      To work around this the following service fields have been moved to the
      database (instead of being hardcoded):
      * category
      * default
      This in turn means we can get the external issue tracker using the
      following query:
          SELECT *
          FROM services
          WHERE active IS TRUE
          AND default IS FALSE
          AND category = 'issue_tracker'
          AND project_id = XXX
          LIMIT 1
      This coupled with memoizing the result (just as before this commit)
      greatly reduces the time it takes for Project#external_issue_tracker to
      complete. The exact reduction depends on one's environment, but locally
      the execution time is reduced from roughly 230 ms to only 2 ms (= a
      reduction of almost 180x).
      Fixes gitlab-org/gitlab-ce#10771
  12. 18 Jan, 2016 1 commit
  13. 14 Jan, 2016 2 commits
  14. 13 Jan, 2016 2 commits
  15. 06 Jan, 2016 1 commit
  16. 05 Jan, 2016 1 commit
  17. 04 Jan, 2016 1 commit
  18. 29 Dec, 2015 1 commit
    • Yorick Peterse's avatar
      Write to InfluxDB directly via UDP · 620e7bb3
      Yorick Peterse authored
      This removes the need for Sidekiq and any overhead/problems introduced
      by TCP. There are a few things to take into account:
      1. When writing data to InfluxDB you may still get an error if the
         server becomes unavailable during the write. Because of this we're
         catching all exceptions and just ignore them (for now).
      2. Writing via UDP apparently requires the timestamp to be in
         nanoseconds. Without this data either isn't written properly.
      3. Due to the restrictions on UDP buffer sizes we're writing metrics one
         by one, instead of writing all of them at once.
  19. 28 Dec, 2015 2 commits
  20. 24 Dec, 2015 3 commits
  21. 14 Dec, 2015 1 commit
  22. 11 Dec, 2015 3 commits