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
path: root/app/workers/repository_check
AgeCommit message (Collapse)Author
2021-07-20Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42GitLab Bot
2021-05-19Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot
2020-07-20Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot
2020-06-18Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot
2020-04-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2018-09-11Disable existing offenses for the CodeReuse copsYorick Peterse
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
2018-07-22Enable frozen string in newly added filesgfyoung
Enables frozen string for new files in directories that had been previously covered in previous MR's. Partially addresses #47424.
2018-07-06Add ExclusiveLease guards for RepositoryCheck::{DispatchWorker,BatchWorker}Stan Hu
We saw in production that DispatchWorker was running about twice an hour, which would schedule twice as many jobs as it should. For some reason, BatchWorker was running 1000 times per hour, possibly due to Sidekiq RSS kills that caused these jobs to restart. Adding an ExclusiveLease prevents these jobs from running more than they should. Relates to https://gitlab.com/gitlab-com/infrastructure/issues/4526
2018-06-27Rename method to #each_eligible_shardToon Claes
2018-06-27Add RepositoryCheck::DispatchWorker to start worker per shardToon Claes
The RepositoryCheck::DispatchWorker will start a RepositoryCheck::BatchWorker for each healthy shard. Closes gitlab-org/gitlab-ce#48042
2018-06-27Enable frozen string for app/workers/**/*.rbgfyoung
Partially addresses #47424.
2018-05-07Use push events again to determine if repo needs checkingToon Claes
2018-05-07Rename methods to make it more clear what they doToon Claes
2018-05-07Refactor RepositoryCheck::BatchWorkerToon Claes
For easier overriding methods.
2018-05-07Pass the result as a positive boolToon Claes
2018-05-07Fix incorrect break statementToon Claes
2018-05-07Due to caching, there is no need to check the settings every loopToon Claes
2018-05-07Make it easier to override how to save the resultsToon Claes
2018-05-07Refactor RepositoryCheck::SingleRepositoryWorkerToon Claes
A repo does not need pushes before it will be repo-checked. There are other sources where commits can come from (e.g. import or webIDE). In the test I made the method of breaking a repo more robust. And added a few test examples. See also gitlab-org/gitlab-ce#45046.
2018-05-07Remove `Rails.env.test?` from production codeToon Claes
2018-01-25Look for rugged with static analysisJacob Vosmaer
2017-12-05Add ApplicationWorker and make every worker include itDouwe Maan
2017-12-04Move SingleRepositoryWorker#fsck into Gitlab::Git::RepositoryKim "BKC" Carlbäcker
2017-06-21Enable Style/DotPosition Rubocop :cop:Grzegorz Bizon
2017-05-10Enable the Style/TrailingCommaInArguments copRémy Coutable
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
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-06-15Do not check repos without push eventsJacob Vosmaer
2016-05-04Merge branch 'create-wikis-during-check' into 'master' Douwe Maan
Initialize wikis on legacy projects during check Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/4173 Helps https://gitlab.com/gitlab-org/gitlab-ce/issues/15423 See merge request !3931
2016-04-26Initialize wikis on legacy projects during checkJacob Vosmaer
2016-04-26Do not fsck projects less than a day oldJacob Vosmaer
This should bring the number of false positives down.
2016-04-18When a project wiki is disabled skip it for fsckJacob Vosmaer
2016-04-14Shut up, RubocopRobert Speicher
2016-04-13Use more conservative limitsJacob Vosmaer
2016-04-13Clear repository check columns asynchronouslyJacob Vosmaer
    generated by cgit v1.2.3 (git 2.25.1) at 2024-08-15 14:42:19 +0300