BigW Consortium Gitlab
This moves the code used for processing commits from GitPushService to its own Sidekiq worker: ProcessCommitWorker. Using a Sidekiq worker allows us to process multiple commits in parallel. This in turn will lead to issues being closed faster and cross references being created faster. Furthermore by isolating this code into a separate class it's easier to test and maintain the code. The new worker also ensures it can efficiently check which issues can be closed, without having to run numerous SQL queries for every issue.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
environments | Loading commit data... | |
initializers | Loading commit data... | |
locales | Loading commit data... | |
routes | Loading commit data... | |
application.rb | Loading commit data... | |
aws.yml.example | Loading commit data... | |
boot.rb | Loading commit data... | |
database.yml.env | Loading commit data... | |
database.yml.mysql | Loading commit data... | |
database.yml.postgresql | Loading commit data... | |
dependency_decisions.yml | Loading commit data... | |
environment.rb | Loading commit data... | |
gitlab.yml.example | Loading commit data... | |
license_finder.yml | Loading commit data... | |
mail_room.yml | Loading commit data... | |
newrelic.yml | Loading commit data... | |
resque.yml.example | Loading commit data... | |
routes.rb | Loading commit data... | |
secrets.yml.example | Loading commit data... | |
sidekiq.yml.example | Loading commit data... | |
sidekiq_queues.yml | Loading commit data... | |
unicorn.rb.example | Loading commit data... | |
unicorn.rb.example.development | Loading commit data... |