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
AgeCommit message (Collapse)Author
2021-05-19Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-01-24Enable the Layout/ExtraSpacing copRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-10-19Remove the `ForkedProjectLink` modelBob Van Landuyt
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.
2018-06-27Enable frozen string literals for app/workers/*.rbgfyoung
2017-12-05Consistently schedule Sidekiq jobsDouwe Maan
2017-12-05Add ApplicationWorker and make every worker include itDouwe Maan
2017-08-25Enable 5 lines of Sidekiq backtrace lines to aid in debuggingStan Hu
Customers often have Sidekiq jobs that failed without much context. Without Sentry, there's no way to tell where these exceptions were hit. Adding in additional lines adds a bit more Redis storage overhead. This commit adds in backtrace logging for workers that delete groups/projects and import/export projects. Closes #27626
2017-08-25Revert "Merge branch 'sh-sidekiq-backtrace' into 'master'"Robert Speicher
This reverts merge request !13813
2017-08-24Enable 5 lines of Sidekiq backtrace lines to aid in debuggingStan Hu
Customers often have Sidekiq jobs that failed without much context. Without Sentry, there's no way to tell where these exceptions were hit. Adding in additional lines adds a bit more Redis storage overhead. This commit adds in backtrace logging for workers that delete groups/projects and import/export projects. Closes #27626
2017-08-22Use EachBatch concern to loop over batchesToon Claes
2017-08-22Migration to remove pending delete projects with non-existing namespaceToon Claes
There might be some projects where the namespace was removed, but the project wasn't. For these the projects still have a `namespace_id` set. So this adds a post-deploy migration remove all projects that are pending delete, and have a `namespace_id` that is non-existing.
2017-08-17Remove a wat in NamespacelessProjectDestroyWorkerNick Thomas
2017-05-10No user needed to cleanup namespaceless pending delete projectsToon Claes
Since this is a cleanup, ran by a post-deploy, there is no need to lookup the admin to run the cleanup.
2017-05-10Use worker to destroy namespaceless projects in post-deployToon Claes
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.