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-05-19Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot
2021-04-21Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43GitLab Bot
2020-06-18Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot
2020-05-29Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot
2020-05-20Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot
2020-03-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2018-06-27Enable frozen string literals for app/workers/*.rbgfyoung
2017-12-05Add ApplicationWorker and make every worker include itDouwe Maan
2017-11-16Adds Rubocop rule for line break after guard clauseJacopo
Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses.
2017-08-01Rename many path_with_namespace -> full_pathGabriel Mazetto
2017-05-09Don't use DiffCollection for deltasJacob Vosmaer
2017-02-23Enable Style/ColonMethodCallDouwe Maan
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-03Use commit deltas when counting files in IrkerWorkerAhmad Sherif
2016-08-03switch from diff_file_collection to diffsPaco Guzman
So we have raw_diffs too
2016-08-03Move to Gitlab::Diff::FileCollectionPaco Guzman
Instead calling diff_collection.count use diff_collection.size which is cache on the diff_collection
2016-03-03Use Gitlab::Git::DiffCollectionsJacob Vosmaer
2015-07-05Add Irker service configuration optionsStan Hu
Closes #1713 Closes #1714 Closes gitlab-com/support-forum#139
2015-04-24Let commit model know about its project.Douwe Maan
2015-03-19Fewer constants, more helpers.Douwe Maan
2015-03-10Use Gitlab::Git helper methods and constants as much as possible.Douwe Maan
2015-03-01Add Irker serviceAorimn
Irker is a gateway which sends IRC messages on git updates. This new service provides an interface to this gateway, integrated in Gitlab, for each updates. As per the guidelines, this commit adds the new feature in the CHANGELOG, tests and documentation. See http://www.catb.org/esr/irker/