0ad80cab40
Destroying projects can be very time consuming. So instead of destroying them in the post-deploy, just schedule them and make Sidekiq do the hard work. They are scheduled in batches of 5000 records. This way the number of database requests is limited while also the amount data read to memory is limited. |
||
|---|---|---|
| .. | ||
| active_record | ||
| add_head_pipeline_for_each_merge_request_spec.rb | ||
| cleanup_namespaceless_pending_delete_projects_spec.rb | ||
| fill_authorized_projects_spec.rb | ||
| migrate_build_events_to_pipeline_events_spec.rb | ||
| migrate_process_commit_worker_jobs_spec.rb | ||
| migrate_user_activities_to_users_last_activity_on_spec.rb | ||
| migrate_user_project_view_spec.rb | ||
| remove_dot_git_from_usernames_spec.rb | ||
| rename_more_reserved_project_names_spec.rb | ||
| rename_reserved_project_names_spec.rb | ||