Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-10-26Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-07-21Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-05-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-04-30Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-04-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-03-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-04-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-24Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-30Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-03-13Run rubocop -aNick Thomas
2018-07-19Improve email address parsingGeorge 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-27Enable frozen string literals for app/workers/*.rbgfyoung
2018-03-07Use Project#full_name instead of name_with_namespaceDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2017-12-05Add ApplicationWorker and make every worker include itDouwe Maan
2017-01-05Prefer leading dots over trailing dotsLin Jen-Shin
2016-12-08Introduce Repository#with_tmp_ref which we needLin Jen-Shin
commits from the other repository. We'll cleanup the tmp ref after we're done with our business.
2016-10-21Re-organize queues to use for SidekiqYorick 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-19Fix force-push message in push emailsSean 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-03switch from diff_file_collection to diffsPaco Guzman
So we have raw_diffs too
2016-08-03Introduce Compare model in the codebase.Paco Guzman
This object will manage Gitlab::Git::Compare instances
2016-07-21Fix emails on push for new and deleted branchesSean McGivern
2016-07-07Represent DiffRefs as proper class instead of tuple arrayDouwe Maan
2016-06-01Make EmailsOnPushWorker use Sidekiq mailers queueStan 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-17Syntax-highlight diffs in push emailsSean McGivern
Based on: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/151
2016-05-11Only generate repository push email onceSean 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-25Rails update to 4.2.4Valery Sizov
2015-08-20Gracefully 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-26Fix EmailsOnPush.Douwe Maan
2015-03-23Clean up code by using keyword arguments.Douwe Maan
2015-03-18Send EmailsOnPush email when branch or tag is created or deleted.Douwe Maan
2015-03-10Use Gitlab::Git helper methods and constants as much as possible.Douwe Maan
2015-02-25Send EmailsOnPush when deleting commits using force push.Douwe Maan
See #1924.
2015-02-25Add option to disable code diffs to EmailOnPush.Douwe Maan
See #1950
2015-02-25Add option to send EmailsOnPush from committer email if domain matches.Douwe Maan
See #1809.
2014-11-14Run 'GC.start' after every EmailsOnPushWorker jobJacob Vosmaer
2014-07-29Git::Compare does not have limit param any moreDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2014-02-12Improve compare logic for EmailOnPush serviceDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2013-12-18Move EmailOnPush logic to async workerDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>