| Age | Commit message (Collapse) | Author |
|---|
|
|
|
used path
|
|
'32677-migrations-using-update_column_in_batches-must-have-a-spec' into 'master'
New Migration/UpdateColumnInBatches cop
Closes #32677
See merge request !11611
|
|
Rework project authorizations and nested groups for better performance
See merge request !10885
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
- Do not care about error when creating index on PostgreSQL
- Test against PostgreSQL 9.2
|
|
> Mysql2::Error: Table 'ci_builds' is specified twice, both as a target for 'UPDATE' and as a separate source for data: UPDATE `ci_builds` SET `retried` = ((SELECT MAX(ci_builds2.id)
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/32647
|
|
Fix incorrect renaming migrations
Closes #32526 and #32530
See merge request !11515
|
|
|
|
|
|
|
|
Closes #32469
|
|
|
|
|
|
|
|
|
|
This commit introduces the usage of Common Table Expressions (CTEs) to
efficiently retrieve nested group hierarchies, without having to rely on
the "routes" table (which is an _incredibly_ inefficient way of getting
the data). This requires a patch to ActiveRecord (found in the added
initializer) to work properly as ActiveRecord doesn't support WITH
statements properly out of the box.
Unfortunately MySQL provides no efficient way of getting nested groups.
For example, the old routes setup could easily take 5-10 seconds
depending on the amount of "routes" in a database. Providing vastly
different logic for both MySQL and PostgreSQL will negatively impact the
development process. Because of this the various nested groups related
methods return empty relations when used in combination with MySQL.
For project authorizations the logic is split up into two classes:
* Gitlab::ProjectAuthorizations::WithNestedGroups
* Gitlab::ProjectAuthorizations::WithoutNestedGroups
Both classes get the fresh project authorizations (= as they should be
in the "project_authorizations" table), including nested groups if
PostgreSQL is used. The logic of these two classes is quite different
apart from their public interface. This complicates development a bit,
but unfortunately there is no way around this.
This commit also introduces Gitlab::GroupHierarchy. This class can be
used to get the ancestors and descendants of a base relation, or both by
using a UNION. This in turn is used by methods such as:
* Namespace#ancestors
* Namespace#descendants
* User#all_expanded_groups
Again this class relies on CTEs and thus only works on PostgreSQL. The
Namespace methods will return an empty relation when MySQL is used,
while User#all_expanded_groups will return only the groups a user is a
direct member of.
Performance wise the impact is quite large. For example, on GitLab.com
Namespace#descendants used to take around 580 ms to retrieve data for a
particular user. Using CTEs we are able to reduce this down to roughly 1
millisecond, returning the exact same data.
== On The Fly Refreshing
Refreshing of authorizations on the fly (= when
users.authorized_projects_populated was not set) is removed with this
commit. This simplifies the code, and ensures any queries used for
authorizations are not mutated because they are executed in a Rails
scope (e.g. Project.visible_to_user).
This commit includes a migration to schedule refreshing authorizations
for all users, ensuring all of them have their authorizations in place.
Said migration schedules users in batches of 5000, with 5 minutes
between every batch to smear the load around a bit.
== Spec Changes
This commit also introduces some changes to various specs. For example,
some specs for ProjectTeam assumed that creating a personal project
would _not_ lead to the owner having access, which is incorrect. Because
we also no longer refresh authorizations on the fly for new users some
code had to be added to the "empty_project" factory. This chunk of code
ensures that the owner's permissions are refreshed after creating the
project, something that is normally done in Projects::CreateService.
|
|
|
|
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
|
Foreign key for Pipeline schedule owner
Closes #31932
See merge request !11233
|
|
This reverts merge request !11287
|
|
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
|
|
|
|
|
Set to nullify, so the settings remain if the user is deleted.
Fixes gitlab-org/gitlab-ce#31932
|
|
|
|
|
|
Retried in database
Closes #25737
See merge request !11115
|
|
Since this is a cleanup, ran by a post-deploy, there is no need to lookup the
admin to run the cleanup.
|
|
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.
|
|
|
|
There are many projects in `pending_delete` state, this post-deploy migration
cleans them up.
The script is based on https://gitlab.com/gitlab-org/gitlab-ce/snippets/1648654
and https://gitlab.com/gitlab-org/gitlab-ce/snippets/1611429. The use of these
scripts were described in
https://gitlab.com/gitlab-com/infrastructure/issues/888.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should rename the already created namespace that snuck trough
because the validation was case sensitive
|
|
|
|
This is based on a migration in https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/2073
Rename forbidden child namespaces
|
|
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
activities
Refactored specs and added a post deployment migration to remove the activity users table.
|
|
|
|
files+readme
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
