BigW Consortium Gitlab

  1. 18 Nov, 2016 2 commits
  2. 17 Nov, 2016 2 commits
  3. 16 Nov, 2016 1 commit
  4. 04 Oct, 2016 1 commit
  5. 09 Sep, 2016 1 commit
  6. 31 Aug, 2016 4 commits
  7. 12 Aug, 2016 1 commit
  8. 04 Aug, 2016 1 commit
  9. 02 Aug, 2016 1 commit
  10. 29 Jul, 2016 2 commits
    • Add pipeline_events to Slack service: · d27095a3
      Lin Jen-Shin authored
      Also add Service#event_names so that we don't have to hard code all
      event names in ServiceParams. Note that I don't know why we want to
      call plural on issue_event and merge_request_event so that we still
      need to hard code them for issues_event and merge_requests_event.
      See app/helpers/services_helper.rb for those special rules.
    • WIP, initial work to implement pipeline hooks: · ae5f124e
      Lin Jen-Shin authored
      I might be squashing this commit in the future.
  11. 21 Jul, 2016 1 commit
  12. 20 Jul, 2016 1 commit
  13. 19 Jul, 2016 2 commits
  14. 15 Jul, 2016 1 commit
  15. 29 Jun, 2016 1 commit
  16. 16 Jun, 2016 2 commits
  17. 15 Jun, 2016 1 commit
    • Set inverse_of for Project/Services relation · 8a9164bf
      Yorick Peterse authored
      This ensures that code such as this don't run needless SQL queries:
      
          project.gitlab_issue_tracker_service.project
      
      This also means that if the root `project` eager loads any associations
      the Service object will be able to re-use those.
  18. 10 Jun, 2016 1 commit
  19. 03 Jun, 2016 2 commits
  20. 09 May, 2016 1 commit
    • Remove the annotate gem and delete old annotations · f1479b56
      Jeroen van Baarsen authored
      In 8278b763 the default behaviour of annotation
      has changes, which was causing a lot of noise in diffs. We decided in #17382
      that it is better to get rid of the whole annotate gem, and instead let people
      look at schema.rb for the columns in a table.
      
      Fixes: #17382
  21. 06 May, 2016 1 commit
  22. 20 Apr, 2016 1 commit
  23. 19 Jan, 2016 1 commit
    • 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
  24. 06 Jan, 2016 1 commit
  25. 11 Dec, 2015 3 commits
  26. 10 Dec, 2015 2 commits
  27. 15 Oct, 2015 1 commit
  28. 14 Oct, 2015 1 commit