Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-07-29 | 1 | -1/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-07-21 | 4 | -0/+8 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-07-12 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-11 | 2 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-04-30 | 4 | -0/+8 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-06-24 | 2 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-06-12 | 1 | -0/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-04-12 | 2 | -4/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-19 | 4 | -4/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-10 | 1 | -1/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-04 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-18 | 1 | -0/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-13 | 2 | -0/+4 |
| | |||||
* | Disable existing offenses for the CodeReuse cops | Yorick Peterse | 2018-09-11 | 3 | -0/+10 |
| | | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop. | ||||
* | Enable frozen string in newly added files | gfyoung | 2018-07-21 | 1 | -0/+2 |
| | | | | | | | | Enables frozen string for new files in directories that had been previously covered in previous MR's. Partially addresses #47424. | ||||
* | Add ExclusiveLease guards for RepositoryCheck::{DispatchWorker,BatchWorker} | Stan Hu | 2018-07-06 | 2 | -4/+29 |
| | | | | | | | | | | | | | 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 | ||||
* | Rename method to #each_eligible_shard | Toon Claes | 2018-06-27 | 1 | -1/+1 |
| | |||||
* | Add RepositoryCheck::DispatchWorker to start worker per shard | Toon Claes | 2018-06-27 | 2 | -4/+28 |
| | | | | | | | The RepositoryCheck::DispatchWorker will start a RepositoryCheck::BatchWorker for each healthy shard. Closes gitlab-org/gitlab-ce#48042 | ||||
* | Enable frozen string for app/workers/**/*.rb | gfyoung | 2018-06-27 | 3 | -0/+6 |
| | | | | Partially addresses #47424. | ||||
* | Use push events again to determine if repo needs checking | Toon Claes | 2018-05-07 | 2 | -18/+16 |
| | |||||
* | Rename methods to make it more clear what they do | Toon Claes | 2018-05-07 | 2 | -12/+14 |
| | |||||
* | Refactor RepositoryCheck::BatchWorker | Toon Claes | 2018-05-07 | 1 | -8/+23 |
| | | | | For easier overriding methods. | ||||
* | Pass the result as a positive bool | Toon Claes | 2018-05-07 | 1 | -3/+4 |
| | |||||
* | Fix incorrect break statement | Toon Claes | 2018-05-07 | 1 | -1/+1 |
| | |||||
* | Due to caching, there is no need to check the settings every loop | Toon Claes | 2018-05-07 | 1 | -1/+2 |
| | |||||
* | Make it easier to override how to save the results | Toon Claes | 2018-05-07 | 1 | -3/+8 |
| | |||||
* | Refactor RepositoryCheck::SingleRepositoryWorker | Toon Claes | 2018-05-07 | 1 | -12/+18 |
| | | | | | | | | | | 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. | ||||
* | Remove `Rails.env.test?` from production code | Toon Claes | 2018-05-07 | 1 | -12/+1 |
| | |||||
* | Look for rugged with static analysislint-rugged | Jacob Vosmaer | 2018-01-25 | 1 | -4/+1 |
| | |||||
* | Add ApplicationWorker and make every worker include it | Douwe Maan | 2017-12-05 | 3 | -3/+3 |
| | |||||
* | Move SingleRepositoryWorker#fsck into Gitlab::Git::Repository | Kim "BKC" Carlbäcker | 2017-12-04 | 1 | -9/+7 |
| | |||||
* | Enable Style/DotPosition Rubocop :cop: | Grzegorz Bizon | 2017-06-21 | 1 | -4/+4 |
| | |||||
* | Enable the Style/TrailingCommaInArguments cop | Rémy Coutable | 2017-05-10 | 2 | -2/+2 |
| | | | | | | Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
* | Re-organize queues to use for Sidekiqseparate-sidekiq-queues | Yorick Peterse | 2016-10-21 | 3 | -15/+12 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | ||||
* | Do not check repos without push events | Jacob Vosmaer | 2016-06-15 | 1 | -1/+5 |
| | |||||
* | Merge branch 'create-wikis-during-check' into 'master' | Douwe Maan | 2016-05-04 | 1 | -11/+23 |
|\ | | | | | | | | | | | | | | | | | 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 | ||||
| * | Initialize wikis on legacy projects during check | Jacob Vosmaer | 2016-04-26 | 1 | -11/+23 |
| | | |||||
* | | Do not fsck projects less than a day old | Jacob Vosmaer | 2016-04-26 | 1 | -2/+2 |
|/ | | | | This should bring the number of false positives down. | ||||
* | When a project wiki is disabled skip it for fsck | Jacob Vosmaer | 2016-04-18 | 1 | -3/+3 |
| | |||||
* | Shut up, Rubocop | Robert Speicher | 2016-04-14 | 1 | -3/+3 |
| | |||||
* | Use more conservative limits | Jacob Vosmaer | 2016-04-13 | 2 | -3/+3 |
| | |||||
* | Clear repository check columns asynchronously | Jacob Vosmaer | 2016-04-13 | 3 | -0/+116 |