BigW Consortium Gitlab

  1. 28 Oct, 2016 1 commit
  2. 27 Oct, 2016 1 commit
  3. 26 Oct, 2016 2 commits
  4. 24 Oct, 2016 2 commits
  5. 22 Oct, 2016 1 commit
  6. 21 Oct, 2016 2 commits
    • 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
    • Change "Group#web_url" to return "/groups/twitter" rather than "/twitter". · c81ff152
      Adam Niedzielski authored
      Bring back the old behaviour which was changed by 6b90ccb9.
      Fixes #23527.
  7. 20 Oct, 2016 1 commit
  8. 19 Oct, 2016 3 commits
  9. 17 Oct, 2016 3 commits
  10. 16 Oct, 2016 1 commit
  11. 15 Oct, 2016 3 commits
  12. 14 Oct, 2016 5 commits
  13. 13 Oct, 2016 3 commits
    • Refactor JS code · a8ac9089
      Alfredo Sumaran authored
      - Use a store base object to manage application state.
      - Add a service to handle ajax requests.
      - Load code only when needed
    • Allow setting content for resolutions · 3f71c43e
      Sean McGivern authored
      When reading conflicts:
      
      1. Add a `type` field. `text` works as before, and has `sections`;
         `text-editor` is a file with ambiguous conflict markers that can only
         be resolved in an editor.
      2. Add a `content_path` field pointing to a JSON representation of the
         file's content for a single file.
      3. Hitting `content_path` returns a similar datastructure to the `file`,
         but without the `content_path` and `sections` fields, and with a
         `content` field containing the full contents of the file (with
         conflict markers).
      
      When writing conflicts:
      
      1. Instead of `sections` being at the top level, they are now in a
         `files` array. This matches the read format better.
      2. The `files` array contains file hashes, each of which must contain:
         a. `new_path`
         b. `old_path`
         c. EITHER `sections` (which works as before) or `content` (with the
            full content of the resolved file).
    • Add instrumentation to conflict classes · 5c525933
      Sean McGivern authored
  14. 12 Oct, 2016 1 commit
  15. 11 Oct, 2016 3 commits
  16. 10 Oct, 2016 2 commits
    • Remove NamespacesController · 66c32cab
      Dmitriy Zaporozhets authored
      The main purpose of this controller was redirect to group or user page
      when URL like https://gitlab.com/gitlab-org was used. Now this
      functionality is handled by contrainers and take user to correct
      controller right from the start
      Signed-off-by: 's avatarDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
    • Precalculate trending projects · 237c8f66
      Yorick Peterse authored
      This commit introduces a Sidekiq worker that precalculates the list of
      trending projects on a daily basis. The resulting set is stored in a
      database table that is then queried by Project.trending.
      
      This setup means that Unicorn workers no longer _may_ have to calculate
      the list of trending projects. Furthermore it supports filtering without
      any complex caching mechanisms.
      
      The data in the "trending_projects" table is inserted in the same order
      as the project ranking. This means that getting the projects in the
      correct order is simply a matter of:
      
          SELECT projects.*
          FROM projects
          INNER JOIN trending_projects ON trending_projects.project_id = projects.id
          ORDER BY trending_projects.id ASC;
      
      Such a query will only take a few milliseconds at most (as measured on
      GitLab.com), opposed to a few seconds for the query used for calculating
      the project ranks.
      
      The migration in this commit does not require downtime and takes care of
      populating an initial list of trending projects.
  17. 08 Oct, 2016 1 commit
  18. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
  19. 06 Oct, 2016 4 commits