Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-10-26 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-07-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-05-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-04-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-04-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-03-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-03-13 | Run rubocop -a | Nick Thomas | |
2018-07-19 | Improve email address parsing | George Thomas | |
If you enter the following RFC 2822 compliant address: `John Doe <john@doe.com>` Gitlab will attempt to send three emails: 1) John 2) Doe 3) john@doe.com With this change given the following: `John Doe <johndoe@example.com>` `Jane Doe <janedoe@example.com>` Gitlab will send emails to `johndoe@example.com` and `janedoe@example.com` | |||
2018-06-27 | Enable frozen string literals for app/workers/*.rb | gfyoung | |
2018-03-07 | Use Project#full_name instead of name_with_namespace | Dmitriy Zaporozhets | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||
2017-12-05 | Add ApplicationWorker and make every worker include it | Douwe Maan | |
2017-01-05 | Prefer leading dots over trailing dots | Lin Jen-Shin | |
2016-12-08 | Introduce Repository#with_tmp_ref which we need | Lin Jen-Shin | |
commits from the other repository. We'll cleanup the tmp ref after we're done with our business. | |||
2016-10-21 | Re-organize queues to use for Sidekiq | Yorick Peterse | |
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 | |||
2016-08-19 | Fix force-push message in push emails | Sean McGivern | |
`after_sha` maps to the source branch, as it's the head of our compare, so these were just the wrong way around. | |||
2016-08-03 | switch from diff_file_collection to diffs | Paco Guzman | |
So we have raw_diffs too | |||
2016-08-03 | Introduce Compare model in the codebase. | Paco Guzman | |
This object will manage Gitlab::Git::Compare instances | |||
2016-07-21 | Fix emails on push for new and deleted branches | Sean McGivern | |
2016-07-07 | Represent DiffRefs as proper class instead of tuple array | Douwe Maan | |
2016-06-01 | Make EmailsOnPushWorker use Sidekiq mailers queue | Stan Hu | |
EmailsOnPushWorker was using the default queue, which made it impossible to prioritize MergeWorker and other key workers with a separate Sidekiq process. | |||
2016-05-17 | Syntax-highlight diffs in push emails | Sean McGivern | |
Based on: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/151 | |||
2016-05-11 | Only generate repository push email once | Sean McGivern | |
The repository push email can be very expensive to generate, especially with syntax-highlighted diffs. Instead of generating the email for each recipient, generate one email object and reset the Message-Id and To headers for each recipient. (Cloning would also be expensive in the case of large emails, although probably not as bad as generating from scratch.) | |||
2015-11-25 | Rails update to 4.2.4 | Valery Sizov | |
2015-08-20 | Gracefully handle SMTP user input errors (e.g. incorrect email addresses) to ↵ | Stan Hu | |
prevent Sidekiq retries Closes https://github.com/gitlabhq/gitlabhq/issues/9560 | |||
2015-03-26 | Fix EmailsOnPush. | Douwe Maan | |
2015-03-23 | Clean up code by using keyword arguments. | Douwe Maan | |
2015-03-18 | Send EmailsOnPush email when branch or tag is created or deleted. | Douwe Maan | |
2015-03-10 | Use Gitlab::Git helper methods and constants as much as possible. | Douwe Maan | |
2015-02-25 | Send EmailsOnPush when deleting commits using force push. | Douwe Maan | |
See #1924. | |||
2015-02-25 | Add option to disable code diffs to EmailOnPush. | Douwe Maan | |
See #1950 | |||
2015-02-25 | Add option to send EmailsOnPush from committer email if domain matches. | Douwe Maan | |
See #1809. | |||
2014-11-14 | Run 'GC.start' after every EmailsOnPushWorker job | Jacob Vosmaer | |
2014-07-29 | Git::Compare does not have limit param any more | Dmitriy Zaporozhets | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||
2014-02-12 | Improve compare logic for EmailOnPush service | Dmitriy Zaporozhets | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | |||
2013-12-18 | Move EmailOnPush logic to async worker | Dmitriy Zaporozhets | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> |