summaryrefslogtreecommitdiff
path: root/app/workers
Commit message (Collapse)AuthorAgeFilesLines
* Remove the `ForkedProjectLink` modelBob Van Landuyt2018-10-191-2/+0
| | | | | | | | | | | | | | This removes the `ForkedProjectLink` model that has been replaced by the `ForkNetworkMember` and `ForkNetwork` combination. All existing relations have been adjusted to use these new models. The `forked_project_link` table has been dropped. The "Forks" count on the admin dashboard has been updated to count all `ForkNetworkMember` rows and deduct the number of `ForkNetwork` rows. This is because now the "root-project" of a fork network also has a `ForkNetworkMember` row. This count could become inaccurate when the root of a fork network is deleted.
* Merge branch 'increase-event-retention-prune-old-events-worker' into 'master'Douwe Maan2018-10-081-4/+3
|\ | | | | | | | | Prune events older than 2 years instead of 12 months See merge request gitlab-org/gitlab-ce!22145
| * Updated code comments for clarity based on 2 yearsJeremy Watson2018-10-061-3/+2
| |
| * prune older than 2 years instead of 12 monthsJeremy Watson2018-10-051-1/+1
| |
* | Revert "Avoid conflicts between enumlator's schedule! method and state ↵Shinya Maeda2018-10-042-2/+2
| | | | | | | | | | | | machine's schedule! method" This reverts commit 10b09db46ddfdc6dfab55fa9671e716cd46a565b.
* | Avoid conflicts between enumlator's schedule! method and state machine's ↵Shinya Maeda2018-10-042-2/+2
| | | | | | | | schedule! method
* | Improve performance of stale scheduled builds searchShinya Maeda2018-10-031-28/+12
| |
* | Rename failure reason to stale_scheduleShinya Maeda2018-10-021-1/+1
| |
* | Cleanup drop_stale_scheduled_builds codeShinya Maeda2018-10-021-2/+7
| |
* | Fix StuckCiJobsWorker and added testsShinya Maeda2018-10-021-1/+1
| |
* | Fix coding style offenceShinya Maeda2018-10-021-8/+8
| |
* | Fix stuck ci jobs workerShinya Maeda2018-10-021-1/+1
| |
* | Simplify StuckCiJobsWorkerShinya Maeda2018-10-021-30/+25
| |
* | Fix stuck job worker. Fix sidekiq queue namespaceShinya Maeda2018-10-022-17/+31
| |
* | Add cleanup mechanizm for stale scheduled jobsShinya Maeda2018-10-021-13/+17
| |
* | Execute the worker in pipeline_processing queueShinya Maeda2018-10-021-0/+4
| |
* | Introduce enqueue_scheduled eventShinya Maeda2018-10-021-4/+3
| |
* | Add a new status to ci_builds.statusShinya Maeda2018-10-021-2/+1
| |
* | Make schedule and unschedule consistentShinya Maeda2018-10-021-6/+3
| |
* | Rename delayed to scheduledShinya Maeda2018-10-022-2/+5
| |
* | Squashed commit of the following:Shinya Maeda2018-10-023-0/+18
|/ | | | | | | | | | | | | | | | | | | | commit 9d9594ba20097dc4598f7eb42a9f9d78d73eae54 Author: Shinya Maeda <shinya@gitlab.com> Date: Thu Sep 13 20:18:31 2018 +0900 Cancel scheduled jobs commit f31c7172e07a9eb03b58c1e62eaa18cda4064aa6 Author: Shinya Maeda <shinya@gitlab.com> Date: Thu Sep 13 11:18:42 2018 +0900 Add Ci::BuildSchedule commit fb6b3ca638f40f9e1ee38b1fdd892bda4f6fede7 Author: Shinya Maeda <shinya@gitlab.com> Date: Wed Sep 12 20:02:50 2018 +0900 Scheduled jobs
* Extend reports to support security featuresOlivier Gonzalez2018-09-271-1/+1
|
* Use standalone diff stats RPC on every comparison viewOswaldo Ferreira2018-09-191-1/+1
|
* Merge branch 'rubocop-code-reuse' into 'master'Robert Speicher2018-09-1355-0/+132
|\ | | | | | | | | Add RuboCop cops to enforce code reusing rules See merge request gitlab-org/gitlab-ce!21391
| * Disable existing offenses for the CodeReuse copsYorick Peterse2018-09-1155-0/+132
| | | | | | | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
* | Log project services errors when executing asyncFelipe Artur2018-09-101-1/+5
|/
* Merge branch 'sh-delete-container-registry-async' into 'master'Robert Speicher2018-09-072-0/+35
|\ | | | | | | | | | | | | Delete a container registry asynchronously Closes #51063 and #49926 See merge request gitlab-org/gitlab-ce!21553
| * Delete a container registry asynchronouslyStan Hu2018-09-072-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | When a container registry has many tags, it's easy for the DELETE call to take more than 60 seconds and fail. This can also leave the registry in a bad state with null bytes since some of the images have been deleted with tags still pointing to them. In addition, we have to prevent users from accidentally initiating the delete multiple times or this could leave the registry with orphaned tags. This commit also adds a flash message to notify the user the registry is scheduled for deletion. Closes #49926, #51063
* | Merge branch 'osw-write-cache-upon-mr-creation-and-cache-refactoring' into ↵Douwe Maan2018-09-071-0/+2
|\ \ | |/ |/| | | | | | | | | | | | | 'master' Write diff highlighting cache upon MR creation (refactors caching) Closes #50204 See merge request gitlab-org/gitlab-ce!21489
| * Cache diff highlighting upon Merge Request creation (refactors diff caching)Oswaldo Ferreira2018-09-071-0/+2
| |
* | Automatically disable Auto DevOps for project upon first pipeline failureMayra Cabrera2018-09-063-0/+46
|/
* Merge branch 'remove-background-migration-worker-feature-flag' into 'master'Douwe Maan2018-08-311-13/+1
|\ | | | | | | | | Remove feature flag from BackgroundMigrationWorker See merge request gitlab-org/gitlab-ce!21404
| * Remove feature flag from BackgroundMigrationWorkerYorick Peterse2018-08-281-13/+1
| | | | | | | | | | | | The feature has been running on GitLab.com for a while now, without any problems. This commit removes the eature flag, and enables the feature for all users.
* | Updates code using class_methods over module ClassMethodsJacopo2018-08-292-2/+2
|/
* Merge branch 'blacklist-destroy-all' into 'master'Robert Speicher2018-08-172-1/+3
|\ | | | | | | | | Blacklist the use of destroy_all See merge request gitlab-org/gitlab-ce!21250
| * Whitelist existing destroy_all offensesblacklist-destroy-allYorick Peterse2018-08-162-1/+3
| | | | | | | | This whitelists all existing places where we use "destroy_all".
* | Merge branch 'zj-remove-repository-languages-feature-gate' into 'master'Nick Thomas2018-08-161-2/+0
|\ \ | |/ |/| | | | | | | | | Remove feature gates for Repository Languages Closes #50291 See merge request gitlab-org/gitlab-ce!21186
| * Remove feature gates for Repository LanguagesZeger-Jan van de Weg2018-08-161-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | The repository languages feature got introduced through: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19480. This MR included feature flags to guard against performance regressions, which allowed GitLab to test it on gitlab.com before the customers would be exposed. .com worked out fine, as shown by our internal monitoring tools, which prompts feature gate removal. Given the docs weren't present yet, these were added too.
* | Enable frozen string in vestigial app filesgfyoung2018-08-126-0/+12
|/ | | | Partially addresses #47424.
* Merge branch 'group-todos' into 'master'Sean McGivern2018-08-072-0/+11
|\ | | | | | | | | Group todos See merge request gitlab-org/gitlab-ce!20675
| * Add changes from the EEJarka Kadlecová2018-08-061-0/+1
| |
| * Remove group todos when a users looses accessJarka Kadlecová2018-08-021-0/+10
| |
* | Merge branch 'background-migrations-system-load' into 'master'Stan Hu2018-08-061-7/+54
|\ \ | | | | | | | | | | | | Respond to DB health in background migrations See merge request gitlab-org/gitlab-ce!20720
| * | Respond to DB health in background migrationsYorick Peterse2018-08-061-7/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the BackgroundMigration worker so it checks for the health of the DB before performing a background migration. This in turn allows us to reduce the minimum interval, without having to worry about blowing things up if we schedule too many migrations. In this setup, the BackgroundMigration worker will reschedule jobs as long as the database is considered to be in an unhealthy state. Once the database has recovered, the migration can be performed. To determine if the database is in a healthy state, we look at the replication lag of any replication slots defined on the primary. If the lag is deemed to great (100 MB by default) for too many slots, the migration is rescheduled for a later point in time. The health checking code is hidden behind a feature flag, allowing us to disable it if necessary.
* | | Resolve "Hashed storage: extend "Enable hashed storage for all new projects" ↵Valery Sizov2018-08-031-2/+2
| | | | | | | | | | | | to "for all new and renamed projects""
* | | Merge branch 'sh-fix-failing-gpg-signature-ce' into 'master'Robert Speicher2018-08-031-0/+4
|\ \ \ | |_|/ |/| | | | | | | | Make CreateGpgSignatureWorker backwards compatible with original method signature (CE port) See merge request gitlab-org/gitlab-ce!20998
| * | Make CreateGpgSignatureWorker backwards compatible with original method ↵Stan Hu2018-08-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | signature Older versions of GitPushService push a single commit SHA string to the queue, but Gitaly requires that the parameters sent by CreateGpgSignatureWorker are an array. It's possible to have old workers using this original signature or jobs in the retry queue that would fail if CreateGpgSignatureWorker can't handle the string form.
* | | Add repository languages for projectsZeger-Jan van de Weg2018-08-012-0/+34
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our friends at GitHub show the programming languages for a long time, and inspired by that this commit means to create about the same functionality. Language detection is done through Linguist, as before, where the difference is that we cache the result in the database. Also, Gitaly can incrementaly scan a repository. This is done through a shell out, which creates overhead of about 3s each run. For now this won't be improved. Scans are triggered by pushed to the default branch, usually `master`. However, one exception to this rule the charts page. If we're requesting this expensive data anyway, we just cache it in the database. Edge cases where there is no repository, or its empty are caught in the Repository model. This makes use of Redis caching, which is probably already loaded. The added model is called RepositoryLanguage, which will make it harder if/when GitLab supports multiple repositories per project. However, for now I think this shouldn't be a concern. Also, Language could be confused with the i18n languages and felt like the current name was suiteable too. Design of the Project#Show page is done with help from @dimitrieh. This change is not visible to the end user unless detections are done.
* | Merge branch 'fj-6860-instance-level-project-templates' into 'master'Sean McGivern2018-08-011-5/+11
|\ \ | |/ |/| | | | | [CE Port]: Implement instance level project templates See merge request gitlab-org/gitlab-ce!20761
| * Code review comment appliedFrancisco Javier López2018-07-231-2/+2
| |
View Lorry Controller Status