summaryrefslogtreecommitdiff
path: root/spec/workers/mail_scheduler
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-06-242-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-251-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-051-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-171-0/+1
|
* Add frozen_string_literal to spec/workersfrozen_string_spec_workersThong Kuah2019-04-012-0/+4
| | | | Adds `# frozen_string_literal: true` to spec/workers ruby files
* Make `ActionContorller::Parameters` serializable for sidekiq jobsPeter Leitzen2019-02-051-5/+44
|
* Bump Ruby on Rails to 5.0.7.1blackst0ne-bump-rails-cve-2018-16476blackst0ne2018-12-211-3/+14
| | | | Fix the CVE-2018-16476 vulnerability.
* Move NotificationService calls to SidekiqSean McGivern2018-04-252-2/+46
| | | | | | | | | | | | | | | | | | | | | The NotificationService has to do quite a lot of work to calculate the recipients for an email. Where possible, we should try to avoid doing this in an HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to schedule those emails immediately. This commit creates a generic Sidekiq worker that uses Global ID to serialise and deserialise its arguments, then forwards them to the NotificationService. The NotificationService gains an `#async` method, so you can replace: notification_service.new_issue(issue, current_user) With: notification_service.async.new_issue(issue, current_user) And have everything else work as normal, except that calculating the recipients will be done by Sidekiq, which will then schedule further Sidekiq jobs to send each email.
* Send emails for issues due tomorrowSean McGivern2018-03-301-0/+21
Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project.