gitlab-org--gitlab-foss/Gemfile

412 lines
9.4 KiB
Text
Raw Normal View History

2016-07-01 19:14:12 -04:00
source 'https://rubygems.org'
2011-10-08 17:36:38 -04:00
2017-02-21 12:01:53 -05:00
gem 'rails', '4.2.8'
2015-11-26 08:48:01 -05:00
gem 'rails-deprecated_sanitizer', '~> 1.0.3'
2015-11-25 11:18:44 -05:00
# Responders respond_to and respond_with
gem 'responders', '~> 2.0'
gem 'sprockets', '~> 3.7.0'
# Default values for AR models
2016-07-01 19:14:12 -04:00
gem 'default_value_for', '~> 3.0.0'
2012-06-20 06:45:26 -04:00
# Supported DBs
2017-07-13 23:17:03 -04:00
gem 'mysql2', '~> 0.4.5', group: :mysql
2016-07-01 19:14:12 -04:00
gem 'pg', '~> 0.18.2', group: :postgres
2012-06-20 06:45:26 -04:00
gem 'rugged', '~> 0.26.0'
gem 'grape-route-helpers', '~> 2.1.0'
2017-01-04 13:43:06 -05:00
gem 'faraday', '~> 0.12'
2017-04-11 21:29:30 -04:00
2015-06-30 15:25:36 -04:00
# Authentication libraries
2017-02-08 13:41:27 -05:00
gem 'devise', '~> 4.2'
gem 'doorkeeper', '~> 4.2.0'
gem 'doorkeeper-openid_connect', '~> 1.1.0'
2017-02-08 13:41:27 -05:00
gem 'omniauth', '~> 1.4.2'
gem 'omniauth-auth0', '~> 1.4.1'
gem 'omniauth-azure-oauth2', '~> 0.0.9'
gem 'omniauth-cas3', '~> 1.1.4'
2017-02-08 13:41:27 -05:00
gem 'omniauth-facebook', '~> 4.0.0'
gem 'omniauth-github', '~> 1.1.1'
gem 'omniauth-gitlab', '~> 1.0.2'
gem 'omniauth-google-oauth2', '~> 0.5.2'
2017-02-08 13:41:27 -05:00
gem 'omniauth-kerberos', '~> 0.3.0', group: :kerberos
gem 'omniauth-oauth2-generic', '~> 0.2.2'
2017-02-08 13:41:27 -05:00
gem 'omniauth-saml', '~> 1.7.0'
gem 'omniauth-shibboleth', '~> 1.2.0'
gem 'omniauth-twitter', '~> 1.2.0'
gem 'omniauth_crowd', '~> 2.2.0'
gem 'omniauth-authentiq', '~> 0.3.1'
2017-02-08 13:41:27 -05:00
gem 'rack-oauth2', '~> 1.2.1'
gem 'jwt', '~> 1.5.6'
2012-06-20 06:45:26 -04:00
# Spam and anti-bot protection
gem 'recaptcha', '~> 3.0', require: 'recaptcha/rails'
gem 'akismet', '~> 2.0'
2015-03-27 18:35:26 -04:00
# Two-factor authentication
gem 'devise-two-factor', '~> 3.0.0'
2015-08-25 21:42:46 -04:00
gem 'rqrcode-rails3', '~> 0.1.7'
gem 'attr_encrypted', '~> 3.0.0'
gem 'u2f', '~> 0.2.1'
2015-03-27 18:35:26 -04:00
2016-02-09 12:06:55 -05:00
# GitLab Pages
gem 'validates_hostname', '~> 1.0.6'
2016-02-09 12:06:55 -05:00
# Browser detection
2016-07-01 19:14:12 -04:00
gem 'browser', '~> 2.2'
2017-02-14 19:01:30 -05:00
# GPG
gem 'gpgme'
# LDAP Auth
# GitLab fork with several improvements to original library. For full list of changes
# see https://github.com/intridea/omniauth-ldap/compare/master...gitlabhq:master
gem 'gitlab_omniauth-ldap', '~> 2.0.4', require: 'omniauth-ldap'
gem 'net-ldap'
# Git Wiki
2016-02-28 07:11:43 -05:00
# Required manually in config/initializers/gollum.rb to control load order
gem 'gollum-lib', '~> 4.2', require: false
2017-01-12 07:08:02 -05:00
gem 'gollum-rugged_adapter', '~> 0.4.4', require: false
2012-10-02 09:29:03 -04:00
# Language detection
2016-07-01 19:14:12 -04:00
gem 'github-linguist', '~> 4.7.0', require: 'linguist'
2012-10-02 09:29:03 -04:00
2012-08-11 15:59:56 -04:00
# API
gem 'grape', '~> 1.0'
2016-11-21 03:09:19 -05:00
gem 'grape-entity', '~> 0.6.0'
2017-02-08 13:41:27 -05:00
gem 'rack-cors', '~> 0.4.0', require: 'rack/cors'
2012-08-11 15:59:56 -04:00
# Disable strong_params so that Mash does not respond to :permitted?
gem 'hashie-forbidden_attributes'
2012-08-11 15:59:56 -04:00
# Pagination
gem 'kaminari', '~> 1.0'
2012-08-11 15:59:56 -04:00
# HAML
gem 'hamlit', '~> 2.6.1'
2012-08-11 15:59:56 -04:00
# Files attachments
gem 'carrierwave', '~> 1.1'
2013-07-08 02:47:31 -04:00
# Drag and Drop UI
2015-08-25 21:42:46 -04:00
gem 'dropzonejs-rails', '~> 0.7.1'
# for backups
gem 'fog-aws', '~> 1.4'
2017-05-01 16:15:16 -04:00
gem 'fog-core', '~> 1.44'
gem 'fog-google', '~> 0.5'
gem 'fog-local', '~> 0.3'
gem 'fog-openstack', '~> 0.1'
gem 'fog-rackspace', '~> 0.1.1'
gem 'fog-aliyun', '~> 0.1.0'
# for Google storage
gem 'google-api-client', '~> 0.8.6'
2013-05-01 05:41:37 -04:00
# for aws storage
2016-07-01 19:14:12 -04:00
gem 'unf', '~> 0.1.4'
2012-08-11 15:59:56 -04:00
# Seed data
2016-07-01 19:14:12 -04:00
gem 'seed-fu', '~> 2.3.5'
2012-08-11 15:59:56 -04:00
2015-04-29 15:02:41 -04:00
# Markdown and HTML processing
2017-02-08 13:41:27 -05:00
gem 'html-pipeline', '~> 1.11.0'
2017-05-18 23:05:05 -04:00
gem 'deckar01-task_list', '2.0.0'
2017-09-20 11:41:38 -04:00
gem 'gitlab-markup', '~> 1.6.2'
2017-02-08 13:41:27 -05:00
gem 'redcarpet', '~> 3.4'
gem 'RedCloth', '~> 4.3.2'
gem 'rdoc', '~> 4.2'
gem 'org-ruby', '~> 0.9.12'
gem 'creole', '~> 0.5.0'
gem 'wikicloth', '0.8.1'
gem 'asciidoctor', '~> 1.5.2'
gem 'asciidoctor-plantuml', '0.0.7'
2017-02-08 13:41:27 -05:00
gem 'rouge', '~> 2.0'
gem 'truncato', '~> 0.7.9'
2017-04-28 10:53:42 -04:00
gem 'bootstrap_form', '~> 2.7.0'
gem 'nokogiri', '~> 1.8.1'
2014-04-15 11:02:02 -04:00
# Diffs
gem 'diffy', '~> 3.1.0'
2014-04-15 11:02:02 -04:00
# Application server
2013-12-18 11:06:49 -05:00
group :unicorn do
gem 'unicorn', '~> 5.1.0'
gem 'unicorn-worker-killer', '~> 0.4.4'
2013-12-18 11:06:49 -05:00
end
2012-08-11 15:59:56 -04:00
2013-02-14 10:33:20 -05:00
# State machine
2016-07-01 19:14:12 -04:00
gem 'state_machines-activerecord', '~> 0.4.0'
2013-02-14 10:33:20 -05:00
2012-08-11 15:59:56 -04:00
# Issue tags
gem 'acts-as-taggable-on', '~> 4.0'
2012-08-11 15:59:56 -04:00
# Background jobs
2017-04-26 10:59:48 -04:00
gem 'sidekiq', '~> 5.0'
gem 'sidekiq-cron', '~> 0.6.0'
gem 'redis-namespace', '~> 1.5.2'
gem 'sidekiq-limit_fetch', '~> 3.4', require: false
2012-08-11 15:59:56 -04:00
2017-03-29 09:22:40 -04:00
# Cron Parser
gem 'rufus-scheduler', '~> 3.4'
2017-03-29 09:22:40 -04:00
2012-08-11 15:59:56 -04:00
# HTTP requests
2016-07-01 19:14:12 -04:00
gem 'httparty', '~> 0.13.3'
2012-08-11 15:59:56 -04:00
# Colored output to console
gem 'rainbow', '~> 2.2'
2012-08-11 15:59:56 -04:00
2012-11-18 15:51:49 -05:00
# GitLab settings
2015-08-25 21:42:46 -04:00
gem 'settingslogic', '~> 2.0.9'
2011-11-04 03:42:36 -04:00
# Linear-time regex library for untrusted regular expressions
gem 're2', '~> 1.1.1'
2012-08-11 15:59:56 -04:00
# Misc
2015-08-25 21:42:46 -04:00
gem 'version_sorter', '~> 2.1.0'
2012-08-11 15:59:56 -04:00
# Cache
gem 'redis-rails', '~> 5.0.1'
# Redis
gem 'redis', '~> 3.2'
gem 'connection_pool', '~> 2.0'
2013-05-23 14:10:32 -04:00
# HipChat integration
2015-03-30 18:53:24 -04:00
gem 'hipchat', '~> 1.5.0'
2013-05-23 14:10:32 -04:00
2016-01-14 09:20:23 -05:00
# JIRA integration
gem 'jira-ruby', '~> 1.4'
2016-01-14 09:20:23 -05:00
# Flowdock integration
2016-07-01 19:14:12 -04:00
gem 'gitlab-flowdock-git-hook', '~> 1.0.1'
# Gemnasium integration
2016-07-01 19:14:12 -04:00
gem 'gemnasium-gitlab-service', '~> 0.2'
2014-03-18 13:27:03 -04:00
# Slack integration
2016-11-30 09:51:48 -05:00
gem 'slack-notifier', '~> 1.5.1'
2014-03-18 13:27:03 -04:00
# Asana integration
2017-04-11 21:29:30 -04:00
gem 'asana', '~> 0.6.0'
2015-08-04 18:21:12 -04:00
# FogBugz integration
2015-09-15 16:09:32 -04:00
gem 'ruby-fogbugz', '~> 0.2.1'
2015-08-04 18:21:12 -04:00
# Kubernetes integration
gem 'kubeclient', '~> 2.2.0'
# d3
2016-01-01 21:34:49 -05:00
gem 'd3_rails', '~> 3.5.0'
2013-07-10 06:48:03 -04:00
# Sanitize user input
2016-07-01 19:14:12 -04:00
gem 'sanitize', '~> 2.0'
gem 'babosa', '~> 1.0.2'
2013-07-10 06:48:03 -04:00
# Sanitizes SVG input
2016-07-01 19:14:12 -04:00
gem 'loofah', '~> 2.0.3'
# Working with license
gem 'licensee', '~> 8.7.0'
2013-09-24 14:13:25 -04:00
# Protect against bruteforcing
gem 'rack-attack', '~> 4.4.1'
2013-09-24 14:13:25 -04:00
# Ace editor
gem 'ace-rails-ap', '~> 4.1.0'
# Keyboard shortcuts
2015-08-25 21:42:46 -04:00
gem 'mousetrap-rails', '~> 1.4.6'
2014-08-21 04:14:31 -04:00
# Detect and convert string character encoding
2017-08-16 10:25:00 -04:00
gem 'charlock_holmes', '~> 0.7.5'
# Faster JSON
gem 'oj', '~> 2.17.4'
# Parse time & duration
gem 'chronic', '~> 0.10.2'
2016-05-18 16:21:51 -04:00
gem 'chronic_duration', '~> 0.10.6'
2017-04-04 13:47:12 -04:00
gem 'webpack-rails', '~> 0.9.10'
gem 'rack-proxy', '~> 0.6.0'
gem 'sass-rails', '~> 5.0.6'
2016-07-01 19:14:12 -04:00
gem 'uglifier', '~> 2.7.2'
2017-02-08 13:41:27 -05:00
gem 'addressable', '~> 2.3.8'
gem 'bootstrap-sass', '~> 3.3.0'
gem 'font-awesome-rails', '~> 4.7'
gem 'gemojione', '~> 3.3'
2017-02-08 13:41:27 -05:00
gem 'gon', '~> 6.1.0'
gem 'jquery-atwho-rails', '~> 1.3.2'
2017-02-08 13:41:27 -05:00
gem 'jquery-rails', '~> 4.1.0'
gem 'request_store', '~> 1.3'
gem 'select2-rails', '~> 3.5.9'
gem 'virtus', '~> 1.0.1'
gem 'base32', '~> 0.3.0'
2011-10-08 17:36:38 -04:00
# Sentry integration
gem 'sentry-raven', '~> 2.5.3'
gem 'premailer-rails', '~> 1.9.7'
2017-04-12 23:41:46 -04:00
# I18n
gem 'ruby_parser', '~> 3.8', require: false
gem 'rails-i18n', '~> 4.0.9'
2017-04-12 23:41:46 -04:00
gem 'gettext_i18n_rails', '~> 1.8.0'
gem 'gettext_i18n_rails_js', '~> 1.2.0'
2017-04-12 23:41:46 -04:00
gem 'gettext', '~> 3.2.2', require: false, group: :development
# Perf bar
gem 'peek', '~> 1.0.1'
gem 'peek-gc', '~> 0.0.2'
gem 'peek-host', '~> 1.0.0'
gem 'peek-mysql2', '~> 1.1.0', group: :mysql
gem 'peek-performance_bar', '~> 1.3.0'
gem 'peek-pg', '~> 1.3.0', group: :postgres
gem 'peek-rblineprof', '~> 0.2.0'
gem 'peek-redis', '~> 1.2.0'
gem 'peek-sidekiq', '~> 1.0.3'
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
# Metrics
group :metrics do
gem 'allocations', '~> 1.0', require: false, platform: :mri
gem 'method_source', '~> 0.8', require: false
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
gem 'influxdb', '~> 0.2', require: false
# Prometheus
gem 'prometheus-client-mmap', '~>0.7.0.beta14'
2017-07-04 11:28:34 -04:00
gem 'raindrops', '~> 0.18'
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
end
2011-10-27 15:37:17 -04:00
group :development do
gem 'foreman', '~> 0.78.0'
2017-03-25 12:23:23 -04:00
gem 'brakeman', '~> 3.6.0', require: false
2015-08-25 21:42:46 -04:00
gem 'letter_opener_web', '~> 1.3.0'
gem 'rblineprof', '~> 0.3.6', platform: :mri, require: false
2013-10-01 08:15:14 -04:00
# Better errors handler
2017-03-25 12:19:22 -04:00
gem 'better_errors', '~> 2.1.0'
2015-08-25 21:42:46 -04:00
gem 'binding_of_caller', '~> 0.7.2'
# thin instead webrick
gem 'thin', '~> 1.7.0'
2011-10-08 17:36:38 -04:00
end
group :development, :test do
gem 'bullet', '~> 5.5.0', require: !!ENV['ENABLE_BULLET']
gem 'pry-byebug', '~> 3.4.1', platform: :mri
gem 'pry-rails', '~> 0.3.4'
2015-06-17 18:05:48 -04:00
gem 'awesome_print', '~> 1.2.0', require: false
2017-08-03 16:38:29 -04:00
gem 'fuubar', '~> 2.2.0'
2015-08-25 21:42:46 -04:00
2017-02-08 13:41:27 -05:00
gem 'database_cleaner', '~> 1.5.0'
2016-12-08 01:30:07 -05:00
gem 'factory_girl_rails', '~> 4.7.0'
2017-08-03 16:38:29 -04:00
gem 'rspec-rails', '~> 3.6.0'
2017-02-08 13:41:27 -05:00
gem 'rspec-retry', '~> 0.4.5'
gem 'spinach-rails', '~> 0.2.1'
2016-03-09 08:12:08 -05:00
gem 'spinach-rerun-reporter', '~> 0.0.2'
2017-02-08 13:41:27 -05:00
gem 'rspec_profiling', '~> 0.0.5'
2017-04-26 10:46:26 -04:00
gem 'rspec-set', '~> 0.1.3'
gem 'rspec-parameterized'
2012-09-10 02:26:35 -04:00
# Prevent occasions where minitest is not bundled in packaged versions of ruby (see #3826)
2015-08-25 21:42:46 -04:00
gem 'minitest', '~> 5.7.0'
2013-04-04 03:55:43 -04:00
# Generate Fake data
gem 'ffaker', '~> 2.4'
2013-04-04 03:55:43 -04:00
gem 'capybara', '~> 2.15.0'
2015-06-17 18:05:48 -04:00
gem 'capybara-screenshot', '~> 1.0.0'
2017-02-08 13:41:27 -05:00
gem 'poltergeist', '~> 1.9.0'
2013-03-26 05:13:30 -04:00
2017-03-25 12:58:11 -04:00
gem 'spring', '~> 2.0.0'
2017-02-08 13:41:27 -05:00
gem 'spring-commands-rspec', '~> 1.0.4'
gem 'spring-commands-spinach', '~> 1.1.0'
2015-08-25 21:42:46 -04:00
gem 'rubocop', '~> 0.49.1', require: false
gem 'rubocop-rspec', '~> 1.15.1', require: false
gem 'rubocop-gitlab-security', '~> 0.1.0', require: false
2017-07-08 07:12:49 -04:00
gem 'scss_lint', '~> 0.54.0', require: false
2017-08-07 05:08:15 -04:00
gem 'haml_lint', '~> 0.26.0', require: false
2017-03-25 12:57:22 -04:00
gem 'simplecov', '~> 0.14.0', require: false
2017-03-25 12:51:46 -04:00
gem 'flay', '~> 2.8.0', require: false
gem 'bundler-audit', '~> 0.5.0', require: false
gem 'benchmark-ips', '~> 2.3.0', require: false
gem 'license_finder', '~> 2.1.0', require: false
gem 'knapsack', '~> 1.11.0'
gem 'activerecord_sane_schema_dumper', '0.2'
gem 'stackprof', '~> 0.2.10', require: false
2017-07-20 11:32:17 -04:00
gem 'simple_po_parser', '~> 1.1.2', require: false
2011-10-08 17:36:38 -04:00
end
group :test do
gem 'shoulda-matchers', '~> 3.1.2', require: false
gem 'email_spec', '~> 1.6.0'
2016-08-01 13:38:46 -04:00
gem 'json-schema', '~> 2.6.2'
gem 'webmock', '~> 2.3.2'
Fix race conditions for AuthorizedProjectsWorker There were two cases that could be problematic: 1. Because sometimes AuthorizedProjectsWorker would be scheduled in a transaction it was possible for a job to run/complete before a COMMIT; resulting in it either producing an error, or producing no new data. 2. When scheduling jobs the code would not wait until completion. This could lead to a user creating a project and then immediately trying to push to it. Usually this will work fine, but given enough load it might take a few seconds before a user has access. The first one is problematic, the second one is mostly just annoying (but annoying enough to warrant a solution). This commit changes two things to deal with this: 1. Sidekiq scheduling now takes places after a COMMIT, this is ensured by scheduling using Rails' after_commit hook instead of doing so in an arbitrary method. 2. When scheduling jobs the calling thread now waits for all jobs to complete. Solution 2 requires tracking of job completions. Sidekiq provides a way to find a job by its ID, but this involves scanning over the entire queue; something that is very in-efficient for large queues. As such a more efficient solution is necessary. There are two main Gems that can do this in a more efficient manner: * sidekiq-status * sidekiq_status No, this is not a joke. Both Gems do a similar thing (but slightly different), and the only difference in their name is a dash vs an underscore. Both Gems however provide far more than just checking if a job has been completed, and both have their problems. sidekiq-status does not appear to be actively maintained, with the last release being in 2015. It also has some issues during testing as API calls are not stubbed in any way. sidekiq_status on the other hand does not appear to be very popular, and introduces a similar amount of code. Because of this I opted to write a simple home grown solution. After all, all we need is storing a job ID somewhere so we can efficiently look it up; we don't need extra web UIs (as provided by sidekiq-status) or complex APIs to update progress, etc. This is where Gitlab::SidekiqStatus comes in handy. This namespace contains some code used for tracking, removing, and looking up job IDs; all without having to scan over an entire queue. Data is removed explicitly, but also expires automatically just in case. Using this API we can now schedule jobs in a fork-join like manner: we schedule the jobs in Sidekiq, process them in parallel, then wait for completion. By using Sidekiq we can leverage all the benefits such as being able to scale across multiple cores and hosts, retrying failed jobs, etc. The one downside is that we need to make sure we can deal with unexpected increases in job processing timings. To deal with this the class Gitlab::JobWaiter (used for waiting for jobs to complete) will only wait a number of seconds (30 by default). Once this timeout is reached it will simply return. For GitLab.com almost all AuthorizedProjectWorker jobs complete in seconds, only very rarely do we spike to job timings of around a minute. These in turn seem to be the result of external factors (e.g. deploys), in which case a user is most likely not able to use the system anyway. In short, this new solution should ensure that jobs are processed properly and that in almost all cases a user has access to their resources whenever they need to have access.
2017-01-22 12:22:02 -05:00
gem 'test_after_commit', '~> 1.1'
gem 'sham_rack', '~> 1.3.6'
gem 'timecop', '~> 0.8.0'
gem 'concurrent-ruby', '~> 1.0.5'
gem 'test-prof', '~> 0.2.5'
2011-10-08 17:36:38 -04:00
end
gem 'octokit', '~> 4.6.2'
2015-08-18 18:46:36 -04:00
gem 'mail_room', '~> 0.9.1'
2015-08-18 20:02:26 -04:00
gem 'email_reply_trimmer', '~> 0.1'
gem 'html2text'
2015-08-25 21:42:46 -04:00
gem 'ruby-prof', '~> 0.16.2'
2015-08-25 21:42:46 -04:00
# OAuth
gem 'oauth2', '~> 1.4'
2015-08-25 21:42:46 -04:00
# Soft deletion
gem 'paranoia', '~> 2.3.1'
# Health check
2017-03-03 13:44:08 -05:00
gem 'health_check', '~> 2.6.0'
# System information
gem 'vmstat', '~> 2.3.0'
gem 'sys-filesystem', '~> 1.1.6'
# SSH host key support
gem 'net-ssh', '~> 4.1.0'
# Required for ED25519 SSH host key support
group :ed25519 do
gem 'rbnacl-libsodium'
2017-08-22 09:36:17 -04:00
gem 'rbnacl', '~> 4.0'
gem 'bcrypt_pbkdf', '~> 1.0'
end
# Gitaly GRPC client
gem 'gitaly-proto', '~> 0.33.0', require: 'gitaly'
gem 'toml-rb', '~> 0.3.15', require: false
2017-05-31 17:06:01 -04:00
# Feature toggles
gem 'flipper', '~> 0.10.2'
gem 'flipper-active_record', '~> 0.10.2'
# Structured logging
gem 'lograge', '~> 0.5'
gem 'grape_logging', '~> 1.7'