BigW Consortium Gitlab

  1. 31 May, 2017 2 commits
  2. 16 May, 2017 1 commit
  3. 08 May, 2017 1 commit
  4. 05 May, 2017 1 commit
  5. 25 Apr, 2017 1 commit
  6. 29 Mar, 2017 1 commit
  7. 22 Mar, 2017 1 commit
  8. 27 Jan, 2017 1 commit
  9. 17 Nov, 2016 2 commits
  10. 12 Nov, 2016 1 commit
  11. 10 Nov, 2016 1 commit
    • [ci skip] Establish basic structure for ux_guide README.md · 11510bf7
      awhildy authored
      Block out pages needed for ux_guide
      
      Add resources stub to ux_guide home
      
      Fill out principles and basics
      
      Add TOC to basics
      
      Move all of UI guide to new UX guide structure
      
      Add first level structure on ux-guide pages
      
      Add more details to buttons
      
      Add button images. Update link on development
      
      Renamed surfaces to templates. Add tooltip details
      
      Update typography and icons on Basics page
      
      Add images for color. First draft of voice and tone
      
      Delete findings page
      
      Refine pages. Fill out Surfaces pages
      
      Clean up layout on basics, surfaces, features. Add anchorlinks and counts to components
      
      Fill out components page
      
      Add item title and system info block
      
      Fill out Features page
      
      Switch tooltip placement image
  12. 31 Oct, 2016 2 commits
  13. 21 Oct, 2016 1 commit
    • Re-organize queues to use for Sidekiq · 97731760
      Yorick Peterse authored
      Dumping too many jobs in the same queue (e.g. the "default" queue) is a
      dangerous setup. Jobs that take a long time to process can effectively
      block any other work from being performed given there are enough of
      these jobs.
      
      Furthermore it becomes harder to monitor the jobs as a single queue
      could contain jobs for different workers. In such a setup the only
      reliable way of getting counts per job is to iterate over all jobs in a
      queue, which is a rather time consuming process.
      
      By using separate queues for various workers we have better control over
      throughput, we can add weight to queues, and we can monitor queues
      better. Some workers still use the same queue whenever their work is
      related. For example, the various CI pipeline workers use the same
      "pipeline" queue.
      
      This commit includes a Rails migration that moves Sidekiq jobs from the
      old queues to the new ones. This migration also takes care of doing the
      inverse if ever needed. This does require downtime as otherwise new jobs
      could be scheduled in the old queues after this migration completes.
      
      This commit also includes an RSpec test that blacklists the use of the
      "default" queue and ensures cron workers use the "cronjob" queue.
      
      Fixes gitlab-org/gitlab-ce#23370
  14. 13 Oct, 2016 1 commit
  15. 22 Sep, 2016 1 commit
  16. 22 Aug, 2016 1 commit
    • Added performance guidelines for new MRs · e4e03d94
      Yorick Peterse authored
      These guidelines cover the performance requirement for newly submitted
      merge requests. These guidelines are put in to place to prevent merge
      requests from negatively impacting GitLab performance as much as
      possible.
  17. 11 Aug, 2016 1 commit
  18. 10 Aug, 2016 1 commit
  19. 08 Aug, 2016 1 commit
  20. 04 Aug, 2016 2 commits
  21. 06 Jun, 2016 2 commits
  22. 30 Apr, 2016 1 commit
  23. 10 Apr, 2016 1 commit
  24. 06 Apr, 2016 1 commit
  25. 02 Apr, 2016 1 commit
  26. 10 Mar, 2016 1 commit
  27. 08 Mar, 2016 1 commit
  28. 17 Feb, 2016 3 commits
  29. 05 Oct, 2015 1 commit
  30. 18 May, 2015 1 commit
  31. 11 May, 2015 1 commit
  32. 08 Mar, 2015 1 commit
  33. 01 Dec, 2014 1 commit