kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/workers/all_queues.yml

132 lines
3.9 KiB
YAML
Raw Normal View History

Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
---
Automatically disable Auto DevOps for project upon first pipeline failure
2018-09-06 15:20:42 -04:00
- auto_devops:auto_devops_disable
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- cronjob:admin_email
- cronjob:expire_build_artifacts
- cronjob:gitlab_usage_ping
- cronjob:import_export_project_cleanup
Add DNS verification to Pages custom domains
2018-02-06 08:25:46 -05:00
- cronjob:pages_domain_verification_cron
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- cronjob:pipeline_schedule
- cronjob:prune_old_events
- cronjob:remove_expired_group_links
- cronjob:remove_expired_members
- cronjob:remove_old_web_hook_logs
- cronjob:remove_unreferenced_lfs_objects
- cronjob:repository_archive_cache
Add RepositoryCheck::DispatchWorker to start worker per shard The RepositoryCheck::DispatchWorker will start a RepositoryCheck::BatchWorker for each healthy shard. Closes gitlab-org/gitlab-ce#48042
2018-06-26 09:12:29 -04:00
- cronjob:repository_check_dispatch
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- cronjob:requests_profiles
- cronjob:stuck_ci_jobs
- cronjob:stuck_import_jobs
- cronjob:stuck_merge_jobs
Rename worker to ArchiveTracesCronWorker
2018-06-06 07:18:32 -04:00
- cronjob:ci_archive_traces_cron
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- cronjob:trending_projects
Send emails for issues due tomorrow Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project.
2018-03-30 09:05:20 -04:00
- cronjob:issue_due_scheduler
Prune web hook logs older than 90 days This adds a recurring Sidekiq job that removes up to 50 000 old web hook logs per hour, if they are older than 90 days. This will prevent the web_hook_logs table from growing indefinitely. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/46120
2018-06-26 12:24:42 -04:00
- cronjob:prune_web_hook_logs
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- gcp_cluster:cluster_install_app
- gcp_cluster:cluster_provision
- gcp_cluster:cluster_wait_for_app_installation
- gcp_cluster:wait_for_cluster_creation
Persist external IP of ingress controller created for GKE (#42643)
2018-02-11 22:22:15 -05:00
- gcp_cluster:cluster_wait_for_ingress_ip_address
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- github_import_advance_stage
- github_importer:github_import_import_diff_note
- github_importer:github_import_import_issue
- github_importer:github_import_import_note
Support LFS objects when creating a project by import
2018-06-06 12:42:18 -04:00
- github_importer:github_import_import_lfs_object
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- github_importer:github_import_import_pull_request
- github_importer:github_import_refresh_import_jid
- github_importer:github_import_stage_finish_import
- github_importer:github_import_stage_import_base_data
- github_importer:github_import_stage_import_issues_and_diff_notes
- github_importer:github_import_stage_import_notes
Support LFS objects when creating a project by import
2018-06-06 12:42:18 -04:00
- github_importer:github_import_stage_import_lfs_objects
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- github_importer:github_import_stage_import_pull_requests
- github_importer:github_import_stage_import_repository
Send emails for issues due tomorrow Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project.
2018-03-30 09:05:20 -04:00
- mail_scheduler:mail_scheduler_issue_due
Move NotificationService calls to Sidekiq The NotificationService has to do quite a lot of work to calculate the recipients for an email. Where possible, we should try to avoid doing this in an HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to schedule those emails immediately. This commit creates a generic Sidekiq worker that uses Global ID to serialise and deserialise its arguments, then forwards them to the NotificationService. The NotificationService gains an `#async` method, so you can replace: notification_service.new_issue(issue, current_user) With: notification_service.async.new_issue(issue, current_user) And have everything else work as normal, except that calculating the recipients will be done by Sidekiq, which will then schedule further Sidekiq jobs to send each email.
2018-04-20 13:37:38 -04:00
- mail_scheduler:mail_scheduler_notification_service
Send emails for issues due tomorrow Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project.
2018-03-30 09:05:20 -04:00
port the object storage to CE
2018-02-21 11:43:21 -05:00
- object_storage:object_storage_background_move
- object_storage:object_storage_migrate_uploads
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- pipeline_cache:expire_job_cache
- pipeline_cache:expire_pipeline_cache
- pipeline_creation:create_pipeline
Add pipeline_creation:run_pipeline_schedule into Sidekiq queue list
2017-12-18 12:00:08 -05:00
- pipeline_creation:run_pipeline_schedule
Integrate two workers into one ArchiveTraceWorker with pipeline_background queue. This queue takes loqer precedence than pipeline_default.
2018-03-06 06:20:36 -05:00
- pipeline_background:archive_trace
Change BuildTraceChunkFlushWorker's queue from pipeline_processing to pipeline_background
2018-05-04 08:48:10 -04:00
- pipeline_background:ci_build_trace_chunk_flush
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- pipeline_default:build_coverage
- pipeline_default:build_trace_sections
- pipeline_default:pipeline_metrics
- pipeline_default:pipeline_notification
Squashed commit of the following: 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
2018-09-17 05:26:22 -04:00
- pipeline_default:ci_build_schedule
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- pipeline_hooks:build_hooks
- pipeline_hooks:pipeline_hooks
- pipeline_processing:build_finished
- pipeline_processing:build_queue
- pipeline_processing:build_success
- pipeline_processing:pipeline_process
- pipeline_processing:pipeline_success
- pipeline_processing:pipeline_update
- pipeline_processing:stage_update
Move update_head_pipeline_for_merge_request queue to pipeline_processing namespace
2018-03-06 11:34:17 -05:00
- pipeline_processing:update_head_pipeline_for_merge_request
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- repository_check:repository_check_clear
Add RepositoryCheck::DispatchWorker to start worker per shard The RepositoryCheck::DispatchWorker will start a RepositoryCheck::BatchWorker for each healthy shard. Closes gitlab-org/gitlab-ce#48042
2018-06-26 09:12:29 -04:00
- repository_check:repository_check_batch
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- repository_check:repository_check_single_repository
Delete todos when users loses target read permissions
2018-07-16 14:30:17 -04:00
- todos_destroyer:todos_destroyer_confidential_issue
- todos_destroyer:todos_destroyer_entity_leave
- todos_destroyer:todos_destroyer_project_private
Remove todos when project feature visibility changes
2018-07-27 05:28:17 -04:00
- todos_destroyer:todos_destroyer_private_features
Add changes from the EE
2018-08-06 05:05:44 -04:00
- todos_destroyer:todos_destroyer_group_private
Delete todos when users loses target read permissions
2018-07-16 14:30:17 -04:00
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- default
- mailers # ActionMailer::DeliveryJob.queue_name
- authorized_projects
- background_migration
- create_gpg_signature
Delete a container registry asynchronously 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
2018-09-06 02:33:30 -04:00
- delete_container_repository
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- delete_merged_branches
- delete_user
- email_receiver
- emails_on_push
- expire_build_instance_artifacts
- git_garbage_collect
- gitlab_shell
- group_destroy
- invalid_gpg_signature_update
- irker
- merge
- namespaceless_project_destroy
- new_issue
- new_merge_request
- new_note
- pages
Add DNS verification to Pages custom domains
2018-02-06 08:25:46 -05:00
- pages_domain_verification
Add plugin queue to all_queues.yml Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2018-02-26 11:17:17 -05:00
- plugin
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- post_receive
- process_commit
- project_cache
- project_destroy
- project_export
- project_migrate_hashed_storage
- project_service
- propagate_service_template
- reactive_caching
Backport 'Rebase' feature from EE to CE When a project uses fast-forward merging strategy user has to rebase MRs to target branch before it can be merged. Now user can do rebase in UI by clicking 'Rebase' button instead of doing rebase locally. This feature was already present in EE, this is only backport of the feature to CE. Couple of changes: * removed rebase license check * renamed migration (changed timestamp) Closes #40301
2017-12-20 04:01:21 -05:00
- rebase
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- repository_fork
- repository_import
Adds remote mirror table migration
2018-05-03 10:19:21 -04:00
- repository_remove_remote
Use a dedicated queue for each worker
2017-11-28 11:16:50 -05:00
- storage_migrator
- system_hook_push
- update_merge_requests
- upload_checksum
- web_hook
Backports every CE related change from ee-5484 to CE
2018-05-03 08:55:14 -04:00
- repository_update_remote_mirror
Persist truncated note diffs on a new table We request Gitaly in a N+1 manner to build discussion diffs. Once the diffs are from different revisions, it's hard to make a single request to the service in order to build the whole response. With this change we solve this problem and simplify a lot fetching this piece of info.
2018-05-16 11:46:18 -04:00
- create_note_diff_file
Delete non-latest merge request diff files upon diffs reload
2018-06-11 16:45:16 -04:00
- delete_diff_files
Add repository languages for projects 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.
2018-06-06 07:10:59 -04:00
- detect_repository_languages
Copy permalink