BigW Consortium Gitlab

  1. 07 Nov, 2016 6 commits
  2. 04 Nov, 2016 1 commit
    • Set default Sidekiq retries to 3 · d498ec98
      Drew Blessing authored
      By default, Sidekiq will retry 25 times with an exponential backoff.
      This may result in jobs retrying for up to 21 days. Most Sidekiq
      failures occur when attempting to connect to external services -
      Project service hooks, web hooks, mailers, mirror updates, etc.
      We should set a default retry of 3, and if that's not sufficient
      individual workers can override this in the worker class.
  3. 01 Nov, 2016 2 commits
    • Update gitlab.yml.example · afc465d9
      Elan Ruusamäe authored
    • Initialize Sidekiq with the list of queues used by GitLab · cde3963d
      Stan Hu authored
      The Sidekiq client API adds an entry to the Sidekiq "queues" list,
      but mail_room and gitlab-shell use redis-rb directly to insert jobs
      into Redis and thus do not make an extra "sadd" call to Redis
      each time a job is inserted. To make it possible to monitor
      these queues via the API, add an initialization step to
      set up the list at startup.
      
      Closes gitlab-com/infrastructure#682
  4. 31 Oct, 2016 1 commit
    • Support for post deployment migrations · 83c82411
      Yorick Peterse authored
      These are regular Rails migrations that are executed by default. A user
      can opt-out of these migrations by setting an environment variable
      during the deployment process.
      
      Fixes gitlab-org/gitlab-ce#22133
  5. 28 Oct, 2016 3 commits
  6. 27 Oct, 2016 1 commit
  7. 26 Oct, 2016 2 commits
  8. 24 Oct, 2016 2 commits
  9. 22 Oct, 2016 1 commit
  10. 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.
  11. 20 Oct, 2016 1 commit
  12. 19 Oct, 2016 3 commits
  13. 17 Oct, 2016 3 commits
  14. 16 Oct, 2016 1 commit
  15. 15 Oct, 2016 3 commits
  16. 14 Oct, 2016 5 commits
  17. 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