2012-11-22 13:34:16 -05:00
|
|
|
class Namespace < ActiveRecord::Base
|
2017-06-29 02:56:48 -04:00
|
|
|
acts_as_paranoid without_default_scope: true
|
2016-05-28 22:54:17 -04:00
|
|
|
|
2016-10-06 17:17:11 -04:00
|
|
|
include CacheMarkdownField
|
2015-02-05 17:20:55 -05:00
|
|
|
include Sortable
|
2013-03-21 16:11:08 -04:00
|
|
|
include Gitlab::ShellAdapter
|
2017-01-20 06:25:53 -05:00
|
|
|
include Gitlab::CurrentSettings
|
2017-07-17 06:40:17 -04:00
|
|
|
include Gitlab::VisibilityLevel
|
2016-10-31 07:00:53 -04:00
|
|
|
include Routable
|
2017-06-01 17:36:04 -04:00
|
|
|
include AfterCommitQueue
|
2017-07-04 20:19:02 -04:00
|
|
|
include Storage::LegacyNamespace
|
2013-03-21 16:11:08 -04:00
|
|
|
|
2017-02-06 10:16:50 -05:00
|
|
|
# Prevent users from creating unreasonably deep level of nesting.
|
|
|
|
# The number 20 was taken based on maximum nesting level of
|
|
|
|
# Android repo (15) + some extra backup.
|
|
|
|
NUMBER_OF_ANCESTORS_ALLOWED = 20
|
|
|
|
|
2016-10-06 17:17:11 -04:00
|
|
|
cache_markdown_field :description, pipeline: :description
|
|
|
|
|
2017-06-08 11:16:27 -04:00
|
|
|
has_many :projects, dependent: :destroy # rubocop:disable Cop/ActiveRecordDependent
|
2016-11-22 11:58:10 -05:00
|
|
|
has_many :project_statistics
|
2012-11-22 13:34:16 -05:00
|
|
|
belongs_to :owner, class_name: "User"
|
|
|
|
|
2016-10-31 07:00:53 -04:00
|
|
|
belongs_to :parent, class_name: "Namespace"
|
|
|
|
has_many :children, class_name: "Namespace", foreign_key: :parent_id
|
2017-06-08 11:16:27 -04:00
|
|
|
has_one :chat_team, dependent: :destroy # rubocop:disable Cop/ActiveRecordDependent
|
2016-10-31 07:00:53 -04:00
|
|
|
|
2013-09-26 07:49:22 -04:00
|
|
|
validates :owner, presence: true, unless: ->(n) { n.type == "Group" }
|
2015-02-03 00:15:44 -05:00
|
|
|
validates :name,
|
2015-12-07 16:17:24 -05:00
|
|
|
presence: true,
|
2016-12-07 12:15:26 -05:00
|
|
|
uniqueness: { scope: :parent_id },
|
2016-12-02 07:54:57 -05:00
|
|
|
length: { maximum: 255 },
|
|
|
|
namespace_name: true
|
2015-02-03 00:15:44 -05:00
|
|
|
|
2016-12-02 07:54:57 -05:00
|
|
|
validates :description, length: { maximum: 255 }
|
2015-02-03 00:15:44 -05:00
|
|
|
validates :path,
|
2015-12-07 16:17:12 -05:00
|
|
|
presence: true,
|
2016-12-02 07:54:57 -05:00
|
|
|
length: { maximum: 255 },
|
2017-04-12 05:28:23 -04:00
|
|
|
dynamic_path: true
|
2012-11-22 13:34:16 -05:00
|
|
|
|
2017-02-06 10:16:50 -05:00
|
|
|
validate :nesting_level_allowed
|
|
|
|
|
2012-11-22 13:34:16 -05:00
|
|
|
delegate :name, to: :owner, allow_nil: true, prefix: true
|
|
|
|
|
2016-11-21 08:33:58 -05:00
|
|
|
after_commit :refresh_access_of_projects_invited_groups, on: :update, if: -> { previous_changes.key?('share_with_group_lock') }
|
2016-06-22 17:04:51 -04:00
|
|
|
|
2017-09-01 19:49:09 -04:00
|
|
|
before_create :sync_share_with_group_lock_with_parent
|
|
|
|
before_update :sync_share_with_group_lock_with_parent, if: :parent_changed?
|
2017-09-05 20:10:30 -04:00
|
|
|
after_update :force_share_with_group_lock_on_descendants, if: -> { share_with_group_lock_changed? && share_with_group_lock? }
|
2017-09-01 19:49:09 -04:00
|
|
|
|
2017-07-04 20:19:02 -04:00
|
|
|
# Legacy Storage specific hooks
|
|
|
|
|
|
|
|
after_update :move_dir, if: :path_changed?
|
2017-02-16 02:50:05 -05:00
|
|
|
before_destroy(prepend: true) { prepare_for_destroy }
|
2012-11-21 00:54:05 -05:00
|
|
|
after_destroy :rm_dir
|
2012-11-23 01:11:09 -05:00
|
|
|
|
2017-05-18 09:56:54 -04:00
|
|
|
scope :for_user, -> { where('type IS NULL') }
|
2012-11-22 23:24:09 -05:00
|
|
|
|
2016-11-22 11:58:10 -05:00
|
|
|
scope :with_statistics, -> do
|
|
|
|
joins('LEFT JOIN project_statistics ps ON ps.namespace_id = namespaces.id')
|
|
|
|
.group('namespaces.id')
|
|
|
|
.select(
|
|
|
|
'namespaces.*',
|
|
|
|
'COALESCE(SUM(ps.storage_size), 0) AS storage_size',
|
|
|
|
'COALESCE(SUM(ps.repository_size), 0) AS repository_size',
|
|
|
|
'COALESCE(SUM(ps.lfs_objects_size), 0) AS lfs_objects_size',
|
2017-05-03 07:27:17 -04:00
|
|
|
'COALESCE(SUM(ps.build_artifacts_size), 0) AS build_artifacts_size'
|
2016-11-22 11:58:10 -05:00
|
|
|
)
|
|
|
|
end
|
|
|
|
|
2015-03-24 09:53:30 -04:00
|
|
|
class << self
|
|
|
|
def by_path(path)
|
2015-12-14 21:53:52 -05:00
|
|
|
find_by('lower(path) = :value', value: path.downcase)
|
2015-03-24 09:53:30 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Case insensetive search for namespace by path or name
|
|
|
|
def find_by_path_or_name(path)
|
|
|
|
find_by("lower(path) = :path OR lower(name) = :path", path: path.downcase)
|
|
|
|
end
|
|
|
|
|
2016-03-04 06:06:25 -05:00
|
|
|
# Searches for namespaces matching the given query.
|
|
|
|
#
|
|
|
|
# This method uses ILIKE on PostgreSQL and LIKE on MySQL.
|
|
|
|
#
|
|
|
|
# query - The search query as a String
|
|
|
|
#
|
|
|
|
# Returns an ActiveRecord::Relation
|
2015-03-24 09:53:30 -04:00
|
|
|
def search(query)
|
2016-03-04 06:06:25 -05:00
|
|
|
t = arel_table
|
|
|
|
pattern = "%#{query}%"
|
|
|
|
|
|
|
|
where(t[:name].matches(pattern).or(t[:path].matches(pattern)))
|
2015-03-24 09:53:30 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
def clean_path(path)
|
2015-04-17 06:03:54 -04:00
|
|
|
path = path.dup
|
2015-04-21 09:49:16 -04:00
|
|
|
# Get the email username by removing everything after an `@` sign.
|
2016-08-25 12:48:08 -04:00
|
|
|
path.gsub!(/@.*\z/, "")
|
2015-04-21 09:49:16 -04:00
|
|
|
# Remove everything that's not in the list of allowed characters.
|
2016-08-25 12:48:08 -04:00
|
|
|
path.gsub!(/[^a-zA-Z0-9_\-\.]/, "")
|
|
|
|
# Remove trailing violations ('.atom', '.git', or '.')
|
|
|
|
path.gsub!(/(\.atom|\.git|\.)*\z/, "")
|
|
|
|
# Remove leading violations ('-')
|
|
|
|
path.gsub!(/\A\-+/, "")
|
2015-03-24 09:53:30 -04:00
|
|
|
|
2015-04-21 06:00:08 -04:00
|
|
|
# Users with the great usernames of "." or ".." would end up with a blank username.
|
2015-06-03 08:57:12 -04:00
|
|
|
# Work around that by setting their username to "blank", followed by a counter.
|
2015-04-21 06:00:08 -04:00
|
|
|
path = "blank" if path.blank?
|
|
|
|
|
2017-02-03 07:55:50 -05:00
|
|
|
uniquify = Uniquify.new
|
2017-02-16 02:05:10 -05:00
|
|
|
uniquify.string(path) { |s| Namespace.find_by_path_or_name(s) }
|
2015-03-24 09:53:30 -04:00
|
|
|
end
|
2012-11-27 01:31:15 -05:00
|
|
|
end
|
|
|
|
|
2017-07-17 06:40:17 -04:00
|
|
|
def visibility_level_field
|
|
|
|
:visibility_level
|
|
|
|
end
|
|
|
|
|
2012-11-22 13:34:16 -05:00
|
|
|
def to_param
|
2016-10-31 07:00:53 -04:00
|
|
|
full_path
|
2012-11-22 13:34:16 -05:00
|
|
|
end
|
2012-11-22 23:11:09 -05:00
|
|
|
|
|
|
|
def human_name
|
|
|
|
owner_name
|
|
|
|
end
|
2012-11-23 01:11:09 -05:00
|
|
|
|
2016-05-09 15:41:48 -04:00
|
|
|
def any_project_has_container_registry_tags?
|
2017-04-03 11:48:17 -04:00
|
|
|
all_projects.any?(&:has_container_registry_tags?)
|
2016-05-09 15:41:48 -04:00
|
|
|
end
|
|
|
|
|
2017-08-01 01:45:04 -04:00
|
|
|
def send_update_instructions
|
|
|
|
projects.each do |project|
|
|
|
|
project.send_move_instructions("#{full_path_was}/#{project.path}")
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2013-11-15 08:25:37 -05:00
|
|
|
def kind
|
|
|
|
type == 'Group' ? 'group' : 'user'
|
|
|
|
end
|
2014-11-14 09:06:39 -05:00
|
|
|
|
|
|
|
def find_fork_of(project)
|
2015-12-14 21:53:52 -05:00
|
|
|
projects.joins(:forked_project_link).find_by('forked_project_links.forked_from_project_id = ?', project.id)
|
2014-11-14 09:06:39 -05:00
|
|
|
end
|
2016-06-22 17:04:51 -04:00
|
|
|
|
2016-09-01 19:49:48 -04:00
|
|
|
def lfs_enabled?
|
|
|
|
# User namespace will always default to the global setting
|
|
|
|
Gitlab.config.lfs.enabled
|
|
|
|
end
|
|
|
|
|
2017-01-20 06:25:53 -05:00
|
|
|
def shared_runners_enabled?
|
|
|
|
projects.with_shared_runners.any?
|
|
|
|
end
|
|
|
|
|
Use CTEs for nested groups and authorizations
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.
2017-04-24 11:19:22 -04:00
|
|
|
# Returns all the ancestors of the current namespaces.
|
2017-01-05 07:43:50 -05:00
|
|
|
def ancestors
|
2017-05-03 08:49:37 -04:00
|
|
|
return self.class.none unless parent_id
|
2017-01-05 07:43:50 -05:00
|
|
|
|
2017-06-21 09:48:12 -04:00
|
|
|
Gitlab::GroupHierarchy
|
|
|
|
.new(self.class.where(id: parent_id))
|
|
|
|
.base_and_ancestors
|
2017-01-05 07:43:50 -05:00
|
|
|
end
|
|
|
|
|
2017-08-11 10:19:11 -04:00
|
|
|
def self_and_ancestors
|
|
|
|
return self.class.where(id: id) unless parent_id
|
|
|
|
|
|
|
|
Gitlab::GroupHierarchy
|
|
|
|
.new(self.class.where(id: id))
|
|
|
|
.base_and_ancestors
|
|
|
|
end
|
|
|
|
|
Use CTEs for nested groups and authorizations
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.
2017-04-24 11:19:22 -04:00
|
|
|
# Returns all the descendants of the current namespace.
|
2017-01-05 07:43:50 -05:00
|
|
|
def descendants
|
2017-06-21 09:48:12 -04:00
|
|
|
Gitlab::GroupHierarchy
|
|
|
|
.new(self.class.where(parent_id: id))
|
|
|
|
.base_and_descendants
|
2016-12-08 11:30:11 -05:00
|
|
|
end
|
|
|
|
|
2017-08-11 10:19:11 -04:00
|
|
|
def self_and_descendants
|
|
|
|
Gitlab::GroupHierarchy
|
|
|
|
.new(self.class.where(id: id))
|
|
|
|
.base_and_descendants
|
|
|
|
end
|
|
|
|
|
2017-02-07 08:55:42 -05:00
|
|
|
def user_ids_for_project_authorizations
|
|
|
|
[owner_id]
|
|
|
|
end
|
|
|
|
|
2017-02-04 13:26:11 -05:00
|
|
|
def parent_changed?
|
|
|
|
parent_id_changed?
|
|
|
|
end
|
|
|
|
|
2017-04-03 11:48:17 -04:00
|
|
|
# Includes projects from this namespace and projects from all subgroups
|
|
|
|
# that belongs to this namespace
|
|
|
|
def all_projects
|
|
|
|
Project.inside_path(full_path)
|
|
|
|
end
|
|
|
|
|
2017-04-11 10:21:52 -04:00
|
|
|
def has_parent?
|
|
|
|
parent.present?
|
|
|
|
end
|
|
|
|
|
2017-08-29 06:15:19 -04:00
|
|
|
def subgroup?
|
|
|
|
has_parent?
|
|
|
|
end
|
|
|
|
|
2017-06-23 20:02:33 -04:00
|
|
|
def soft_delete_without_removing_associations
|
|
|
|
# We can't use paranoia's `#destroy` since this will hard-delete projects.
|
|
|
|
# Project uses `pending_delete` instead of the acts_as_paranoia gem.
|
|
|
|
self.deleted_at = Time.now
|
|
|
|
end
|
|
|
|
|
2016-06-22 17:04:51 -04:00
|
|
|
private
|
|
|
|
|
2016-11-21 08:33:58 -05:00
|
|
|
def refresh_access_of_projects_invited_groups
|
2017-06-21 09:48:12 -04:00
|
|
|
Group
|
|
|
|
.joins(project_group_links: :project)
|
|
|
|
.where(projects: { namespace_id: id })
|
|
|
|
.find_each(&:refresh_members_authorized_projects)
|
2016-11-21 08:33:58 -05:00
|
|
|
end
|
2016-10-31 07:00:53 -04:00
|
|
|
|
2017-02-06 10:16:50 -05:00
|
|
|
def nesting_level_allowed
|
|
|
|
if ancestors.count > Group::NUMBER_OF_ANCESTORS_ALLOWED
|
|
|
|
errors.add(:parent_id, "has too deep level of nesting")
|
|
|
|
end
|
|
|
|
end
|
2017-09-01 19:49:09 -04:00
|
|
|
|
|
|
|
def sync_share_with_group_lock_with_parent
|
2017-09-05 20:10:30 -04:00
|
|
|
if parent&.share_with_group_lock?
|
2017-09-01 19:49:09 -04:00
|
|
|
self.share_with_group_lock = true
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
def force_share_with_group_lock_on_descendants
|
2017-09-15 09:34:41 -04:00
|
|
|
return unless Group.supports_nested_groups?
|
|
|
|
|
|
|
|
# We can't use `descendants.update_all` since Rails will throw away the WITH
|
|
|
|
# RECURSIVE statement. We also can't use WHERE EXISTS since we can't use
|
|
|
|
# different table aliases, hence we're just using WHERE IN. Since we have a
|
|
|
|
# maximum of 20 nested groups this should be fine.
|
|
|
|
Namespace.where(id: descendants.select(:id))
|
|
|
|
.update_all(share_with_group_lock: true)
|
2017-09-01 19:49:09 -04:00
|
|
|
end
|
2012-11-22 13:34:16 -05:00
|
|
|
end
|