2012-02-28 13:09:23 +00:00
|
|
|
class Event < ActiveRecord::Base
|
2015-02-05 22:20:55 +00:00
|
|
|
include Sortable
|
2017-08-30 13:38:16 +00:00
|
|
|
include IgnorableColumn
|
2017-09-20 11:36:18 +00:00
|
|
|
default_scope { reorder(nil) }
|
2012-03-07 08:13:43 +00:00
|
|
|
|
2013-02-13 11:48:16 +00:00
|
|
|
CREATED = 1
|
|
|
|
UPDATED = 2
|
|
|
|
CLOSED = 3
|
|
|
|
REOPENED = 4
|
|
|
|
PUSHED = 5
|
|
|
|
COMMENTED = 6
|
|
|
|
MERGED = 7
|
|
|
|
JOINED = 8 # User joined project
|
|
|
|
LEFT = 9 # User left project
|
2015-08-31 04:51:34 +00:00
|
|
|
DESTROYED = 10
|
2016-10-06 15:19:27 +00:00
|
|
|
EXPIRED = 11 # User left project due to expiry
|
2012-02-28 14:01:14 +00:00
|
|
|
|
2017-05-29 05:49:17 +00:00
|
|
|
ACTIONS = HashWithIndifferentAccess.new(
|
|
|
|
created: CREATED,
|
|
|
|
updated: UPDATED,
|
|
|
|
closed: CLOSED,
|
|
|
|
reopened: REOPENED,
|
|
|
|
pushed: PUSHED,
|
|
|
|
commented: COMMENTED,
|
|
|
|
merged: MERGED,
|
|
|
|
joined: JOINED,
|
|
|
|
left: LEFT,
|
|
|
|
destroyed: DESTROYED,
|
|
|
|
expired: EXPIRED
|
|
|
|
).freeze
|
|
|
|
|
|
|
|
TARGET_TYPES = HashWithIndifferentAccess.new(
|
|
|
|
issue: Issue,
|
|
|
|
milestone: Milestone,
|
|
|
|
merge_request: MergeRequest,
|
|
|
|
note: Note,
|
|
|
|
project: Project,
|
|
|
|
snippet: Snippet,
|
|
|
|
user: User
|
|
|
|
).freeze
|
|
|
|
|
2016-09-16 14:05:12 +00:00
|
|
|
RESET_PROJECT_ACTIVITY_INTERVAL = 1.hour
|
|
|
|
|
2017-04-19 23:04:56 +00:00
|
|
|
delegate :name, :email, :public_email, :username, to: :author, prefix: true, allow_nil: true
|
2012-09-27 06:20:36 +00:00
|
|
|
delegate :title, to: :issue, prefix: true, allow_nil: true
|
|
|
|
delegate :title, to: :merge_request, prefix: true, allow_nil: true
|
2014-05-29 14:55:55 +00:00
|
|
|
delegate :title, to: :note, prefix: true, allow_nil: true
|
2012-09-27 06:20:36 +00:00
|
|
|
|
2012-09-27 20:23:11 +00:00
|
|
|
belongs_to :author, class_name: "User"
|
2012-02-28 13:09:23 +00:00
|
|
|
belongs_to :project
|
2018-01-03 16:44:29 +00:00
|
|
|
|
|
|
|
belongs_to :target, -> {
|
|
|
|
# If the association for "target" defines an "author" association we want to
|
|
|
|
# eager-load this so Banzai & friends don't end up performing N+1 queries to
|
2018-03-23 12:58:46 +00:00
|
|
|
# get the authors of notes, issues, etc. (likewise for "noteable").
|
|
|
|
incs = %i(author noteable).select do |a|
|
|
|
|
reflections['events'].active_record.reflect_on_association(a)
|
2018-01-03 16:44:29 +00:00
|
|
|
end
|
2018-03-23 12:58:46 +00:00
|
|
|
|
|
|
|
incs.reduce(self) { |obj, a| obj.includes(a) }
|
2018-01-03 16:44:29 +00:00
|
|
|
}, polymorphic: true # rubocop:disable Cop/PolymorphicAssociations
|
|
|
|
|
2017-09-01 10:50:14 +00:00
|
|
|
has_one :push_event_payload
|
2012-02-28 14:01:14 +00:00
|
|
|
|
2014-06-17 18:23:43 +00:00
|
|
|
# Callbacks
|
|
|
|
after_create :reset_project_activity
|
2017-05-04 01:44:39 +00:00
|
|
|
after_create :set_last_repository_updated_at, if: :push?
|
2018-03-01 14:42:04 +00:00
|
|
|
after_create :track_user_interacted_projects
|
2014-06-17 18:23:43 +00:00
|
|
|
|
2012-10-09 00:10:04 +00:00
|
|
|
# Scopes
|
2015-11-11 14:17:12 +00:00
|
|
|
scope :recent, -> { reorder(id: :desc) }
|
2013-02-13 11:48:16 +00:00
|
|
|
scope :code_push, -> { where(action: PUSHED) }
|
2016-01-25 15:56:23 +00:00
|
|
|
|
2017-07-27 17:42:15 +00:00
|
|
|
scope :in_projects, -> (projects) do
|
|
|
|
sub_query = projects
|
|
|
|
.except(:order)
|
|
|
|
.select(1)
|
|
|
|
.where('projects.id = events.project_id')
|
|
|
|
|
|
|
|
where('EXISTS (?)', sub_query).recent
|
2016-01-25 15:56:23 +00:00
|
|
|
end
|
|
|
|
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
scope :with_associations, -> do
|
|
|
|
# We're using preload for "push_event_payload" as otherwise the association
|
|
|
|
# is not always available (depending on the query being built).
|
|
|
|
includes(:author, :project, project: :namespace)
|
2017-12-22 17:02:48 +00:00
|
|
|
.preload(:target, :push_event_payload)
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
end
|
|
|
|
|
2015-08-31 04:51:34 +00:00
|
|
|
scope :for_milestone_id, ->(milestone_id) { where(target_type: "Milestone", target_id: milestone_id) }
|
2012-02-29 20:38:24 +00:00
|
|
|
|
2017-09-20 11:36:18 +00:00
|
|
|
# Authors are required as they're used to display who pushed data.
|
|
|
|
#
|
|
|
|
# We're just validating the presence of the ID here as foreign key constraints
|
|
|
|
# should ensure the ID points to a valid user.
|
|
|
|
validates :author_id, presence: true
|
|
|
|
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
self.inheritance_column = 'action'
|
|
|
|
|
2012-10-09 00:10:04 +00:00
|
|
|
class << self
|
2017-08-20 21:18:42 +00:00
|
|
|
def model_name
|
|
|
|
ActiveModel::Name.new(self, nil, 'event')
|
|
|
|
end
|
|
|
|
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
def find_sti_class(action)
|
|
|
|
if action.to_i == PUSHED
|
|
|
|
PushEvent
|
|
|
|
else
|
|
|
|
Event
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2018-04-11 11:16:59 +00:00
|
|
|
# Remove this method when removing Gitlab.rails5? code.
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
def subclass_from_attributes(attrs)
|
2018-04-11 11:16:59 +00:00
|
|
|
return super if Gitlab.rails5?
|
|
|
|
|
Migrate events into a new format
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
2017-07-10 15:43:57 +00:00
|
|
|
# Without this Rails will keep calling this method on the returned class,
|
|
|
|
# resulting in an infinite loop.
|
|
|
|
return unless self == Event
|
|
|
|
|
|
|
|
action = attrs.with_indifferent_access[inheritance_column].to_i
|
|
|
|
|
|
|
|
PushEvent if action == PUSHED
|
|
|
|
end
|
|
|
|
|
2016-11-04 14:15:43 +00:00
|
|
|
# Update Gitlab::ContributionsCalendar#activity_dates if this changes
|
2015-03-22 20:55:00 +00:00
|
|
|
def contributions
|
2017-01-26 17:59:50 +00:00
|
|
|
where("action = ? OR (target_type IN (?) AND action IN (?)) OR (target_type = ? AND action = ?)",
|
|
|
|
Event::PUSHED,
|
2017-02-22 17:46:57 +00:00
|
|
|
%w(MergeRequest Issue), [Event::CREATED, Event::CLOSED, Event::MERGED],
|
2017-01-26 17:59:50 +00:00
|
|
|
"Note", Event::COMMENTED)
|
2015-03-22 20:55:00 +00:00
|
|
|
end
|
2015-11-11 16:14:47 +00:00
|
|
|
|
2015-11-18 11:25:37 +00:00
|
|
|
def limit_recent(limit = 20, offset = nil)
|
|
|
|
recent.limit(limit).offset(offset)
|
|
|
|
end
|
2017-05-29 05:49:17 +00:00
|
|
|
|
|
|
|
def actions
|
|
|
|
ACTIONS.keys
|
|
|
|
end
|
|
|
|
|
|
|
|
def target_types
|
|
|
|
TARGET_TYPES.keys
|
|
|
|
end
|
2012-07-20 05:39:34 +00:00
|
|
|
end
|
|
|
|
|
2016-03-24 17:24:22 +00:00
|
|
|
def visible_to_user?(user = nil)
|
2016-11-16 14:17:09 +00:00
|
|
|
if push? || commit_note?
|
2016-11-04 14:15:43 +00:00
|
|
|
Ability.allowed?(user, :download_code, project)
|
2012-12-14 19:39:55 +00:00
|
|
|
elsif membership_changed?
|
|
|
|
true
|
2015-02-13 11:01:28 +00:00
|
|
|
elsif created_project?
|
|
|
|
true
|
2016-03-24 17:20:47 +00:00
|
|
|
elsif issue? || issue_note?
|
2016-08-08 18:55:13 +00:00
|
|
|
Ability.allowed?(user, :read_issue, note? ? note_target : target)
|
2016-10-04 12:52:08 +00:00
|
|
|
elsif merge_request? || merge_request_note?
|
|
|
|
Ability.allowed?(user, :read_merge_request, note? ? note_target : target)
|
2012-12-14 19:39:55 +00:00
|
|
|
else
|
2016-10-04 12:52:08 +00:00
|
|
|
milestone?
|
2012-12-14 19:39:55 +00:00
|
|
|
end
|
2012-03-01 18:47:57 +00:00
|
|
|
end
|
|
|
|
|
2012-09-14 15:46:40 +00:00
|
|
|
def project_name
|
|
|
|
if project
|
2018-03-05 14:15:26 +00:00
|
|
|
project.full_name
|
2012-09-14 15:46:40 +00:00
|
|
|
else
|
2012-09-30 13:04:43 +00:00
|
|
|
"(deleted project)"
|
2012-09-14 15:46:40 +00:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2012-10-01 13:39:19 +00:00
|
|
|
def target_title
|
2016-05-08 18:05:45 +00:00
|
|
|
target.try(:title)
|
2015-02-13 11:00:12 +00:00
|
|
|
end
|
|
|
|
|
|
|
|
def created?
|
|
|
|
action == CREATED
|
2012-10-01 13:39:19 +00:00
|
|
|
end
|
|
|
|
|
2012-02-29 20:38:24 +00:00
|
|
|
def push?
|
2017-08-30 13:38:16 +00:00
|
|
|
false
|
2012-02-29 20:38:24 +00:00
|
|
|
end
|
|
|
|
|
2012-04-01 21:24:45 +00:00
|
|
|
def merged?
|
2015-02-13 11:00:12 +00:00
|
|
|
action == MERGED
|
2012-04-01 21:24:45 +00:00
|
|
|
end
|
|
|
|
|
2012-03-07 08:13:43 +00:00
|
|
|
def closed?
|
2015-02-13 11:00:12 +00:00
|
|
|
action == CLOSED
|
2012-03-07 08:13:43 +00:00
|
|
|
end
|
|
|
|
|
|
|
|
def reopened?
|
2015-02-13 11:00:12 +00:00
|
|
|
action == REOPENED
|
|
|
|
end
|
|
|
|
|
|
|
|
def joined?
|
|
|
|
action == JOINED
|
|
|
|
end
|
|
|
|
|
|
|
|
def left?
|
|
|
|
action == LEFT
|
|
|
|
end
|
|
|
|
|
2016-10-06 15:19:27 +00:00
|
|
|
def expired?
|
|
|
|
action == EXPIRED
|
|
|
|
end
|
|
|
|
|
2015-08-31 04:51:34 +00:00
|
|
|
def destroyed?
|
|
|
|
action == DESTROYED
|
|
|
|
end
|
|
|
|
|
2015-02-13 11:00:12 +00:00
|
|
|
def commented?
|
|
|
|
action == COMMENTED
|
|
|
|
end
|
|
|
|
|
|
|
|
def membership_changed?
|
2016-10-06 15:19:27 +00:00
|
|
|
joined? || left? || expired?
|
2012-03-07 08:13:43 +00:00
|
|
|
end
|
|
|
|
|
2015-02-13 11:01:28 +00:00
|
|
|
def created_project?
|
2015-08-31 04:51:34 +00:00
|
|
|
created? && !target && target_type.nil?
|
2015-02-13 11:01:28 +00:00
|
|
|
end
|
|
|
|
|
|
|
|
def created_target?
|
|
|
|
created? && target
|
|
|
|
end
|
|
|
|
|
2012-12-14 17:33:33 +00:00
|
|
|
def milestone?
|
|
|
|
target_type == "Milestone"
|
|
|
|
end
|
|
|
|
|
|
|
|
def note?
|
2016-07-06 08:08:42 +00:00
|
|
|
target.is_a?(Note)
|
2012-12-14 17:33:33 +00:00
|
|
|
end
|
|
|
|
|
2012-09-14 15:46:40 +00:00
|
|
|
def issue?
|
2012-04-01 21:24:45 +00:00
|
|
|
target_type == "Issue"
|
2012-02-29 20:38:24 +00:00
|
|
|
end
|
|
|
|
|
2012-09-14 15:46:40 +00:00
|
|
|
def merge_request?
|
2012-04-01 21:24:45 +00:00
|
|
|
target_type == "MergeRequest"
|
2012-03-05 22:29:40 +00:00
|
|
|
end
|
|
|
|
|
2015-02-13 11:00:12 +00:00
|
|
|
def milestone
|
|
|
|
target if milestone?
|
2012-09-09 20:18:28 +00:00
|
|
|
end
|
|
|
|
|
2012-09-14 15:46:40 +00:00
|
|
|
def issue
|
2015-02-13 11:00:12 +00:00
|
|
|
target if issue?
|
2012-03-01 20:43:04 +00:00
|
|
|
end
|
|
|
|
|
|
|
|
def merge_request
|
2015-02-13 11:00:12 +00:00
|
|
|
target if merge_request?
|
2012-03-01 20:43:04 +00:00
|
|
|
end
|
|
|
|
|
2014-05-29 14:55:55 +00:00
|
|
|
def note
|
2015-02-13 11:00:12 +00:00
|
|
|
target if note?
|
2014-05-29 14:55:55 +00:00
|
|
|
end
|
|
|
|
|
2012-04-01 21:24:45 +00:00
|
|
|
def action_name
|
2015-02-13 11:00:12 +00:00
|
|
|
if push?
|
2017-09-12 17:27:29 +00:00
|
|
|
push_action_name
|
2015-02-13 11:00:12 +00:00
|
|
|
elsif closed?
|
2012-04-01 21:24:45 +00:00
|
|
|
"closed"
|
|
|
|
elsif merged?
|
2013-04-06 12:53:35 +00:00
|
|
|
"accepted"
|
2012-09-09 20:18:28 +00:00
|
|
|
elsif joined?
|
|
|
|
'joined'
|
2012-09-09 21:27:47 +00:00
|
|
|
elsif left?
|
|
|
|
'left'
|
2016-10-06 15:19:27 +00:00
|
|
|
elsif expired?
|
|
|
|
'removed due to membership expiration from'
|
2015-08-31 04:51:34 +00:00
|
|
|
elsif destroyed?
|
|
|
|
'destroyed'
|
2015-02-13 11:00:12 +00:00
|
|
|
elsif commented?
|
|
|
|
"commented on"
|
2015-02-13 11:01:28 +00:00
|
|
|
elsif created_project?
|
2017-09-12 17:27:29 +00:00
|
|
|
created_project_action_name
|
2012-09-14 15:46:40 +00:00
|
|
|
else
|
2012-04-01 21:24:45 +00:00
|
|
|
"opened"
|
2012-02-29 20:38:24 +00:00
|
|
|
end
|
|
|
|
end
|
2013-01-02 21:35:11 +00:00
|
|
|
|
2013-08-19 19:12:59 +00:00
|
|
|
def target_iid
|
|
|
|
target.respond_to?(:iid) ? target.iid : target_id
|
|
|
|
end
|
|
|
|
|
2016-05-12 20:31:53 +00:00
|
|
|
def commit_note?
|
2016-11-16 14:17:09 +00:00
|
|
|
note? && target && target.for_commit?
|
2013-01-02 21:35:11 +00:00
|
|
|
end
|
|
|
|
|
2016-03-24 17:20:47 +00:00
|
|
|
def issue_note?
|
2016-05-08 18:46:43 +00:00
|
|
|
note? && target && target.for_issue?
|
2016-03-24 17:20:47 +00:00
|
|
|
end
|
|
|
|
|
2016-10-04 12:52:08 +00:00
|
|
|
def merge_request_note?
|
|
|
|
note? && target && target.for_merge_request?
|
|
|
|
end
|
|
|
|
|
2016-05-12 20:37:00 +00:00
|
|
|
def project_snippet_note?
|
2016-11-16 14:17:09 +00:00
|
|
|
note? && target && target.for_snippet?
|
2013-03-25 11:58:09 +00:00
|
|
|
end
|
|
|
|
|
2013-01-02 21:35:11 +00:00
|
|
|
def note_target
|
|
|
|
target.noteable
|
|
|
|
end
|
|
|
|
|
|
|
|
def note_target_id
|
2016-05-12 20:31:53 +00:00
|
|
|
if commit_note?
|
2013-01-02 21:35:11 +00:00
|
|
|
target.commit_id
|
|
|
|
else
|
|
|
|
target.noteable_id.to_s
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2016-05-12 21:47:45 +00:00
|
|
|
def note_target_reference
|
|
|
|
return unless note_target
|
|
|
|
|
|
|
|
# Commit#to_reference returns the full SHA, but we want the short one here
|
|
|
|
if commit_note?
|
|
|
|
note_target.short_id
|
2013-08-19 19:53:11 +00:00
|
|
|
else
|
2016-05-12 21:47:45 +00:00
|
|
|
note_target.to_reference
|
|
|
|
end
|
2013-08-19 19:53:11 +00:00
|
|
|
end
|
|
|
|
|
2013-01-02 21:35:11 +00:00
|
|
|
def note_target_type
|
|
|
|
if target.noteable_type.present?
|
|
|
|
target.noteable_type.titleize
|
|
|
|
else
|
|
|
|
"Wall"
|
|
|
|
end.downcase
|
|
|
|
end
|
2013-08-20 18:31:37 +00:00
|
|
|
|
|
|
|
def body?
|
|
|
|
if push?
|
2017-08-21 15:27:06 +00:00
|
|
|
push_with_commits?
|
2013-08-20 18:31:37 +00:00
|
|
|
elsif note?
|
|
|
|
true
|
|
|
|
else
|
|
|
|
target.respond_to? :title
|
|
|
|
end
|
|
|
|
end
|
2014-06-17 18:23:43 +00:00
|
|
|
|
|
|
|
def reset_project_activity
|
2016-09-16 14:05:12 +00:00
|
|
|
return unless project
|
|
|
|
|
2016-10-04 15:22:58 +00:00
|
|
|
# Don't bother updating if we know the project was updated recently.
|
2016-09-20 02:59:29 +00:00
|
|
|
return if recent_update?
|
2016-09-16 14:05:12 +00:00
|
|
|
|
2016-10-04 15:22:58 +00:00
|
|
|
# At this point it's possible for multiple threads/processes to try to
|
|
|
|
# update the project. Only one query should actually perform the update,
|
|
|
|
# hence we add the extra WHERE clause for last_activity_at.
|
2017-06-21 13:48:12 +00:00
|
|
|
Project.unscoped.where(id: project_id)
|
|
|
|
.where('last_activity_at <= ?', RESET_PROJECT_ACTIVITY_INTERVAL.ago)
|
|
|
|
.update_all(last_activity_at: created_at)
|
2016-09-20 02:59:29 +00:00
|
|
|
end
|
|
|
|
|
2016-11-24 10:25:23 +00:00
|
|
|
def authored_by?(user)
|
|
|
|
user ? author_id == user.id : false
|
|
|
|
end
|
|
|
|
|
2017-08-20 21:18:42 +00:00
|
|
|
def to_partial_path
|
|
|
|
# We are intentionally using `Event` rather than `self.class` so that
|
|
|
|
# subclasses also use the `Event` implementation.
|
|
|
|
Event._to_partial_path
|
|
|
|
end
|
|
|
|
|
2016-09-20 02:59:29 +00:00
|
|
|
private
|
|
|
|
|
2017-09-12 17:27:29 +00:00
|
|
|
def push_action_name
|
|
|
|
if new_ref?
|
|
|
|
"pushed new"
|
|
|
|
elsif rm_ref?
|
|
|
|
"deleted"
|
|
|
|
else
|
|
|
|
"pushed to"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
def created_project_action_name
|
|
|
|
if project.external_import?
|
|
|
|
"imported"
|
|
|
|
else
|
|
|
|
"created"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2016-09-20 02:59:29 +00:00
|
|
|
def recent_update?
|
|
|
|
project.last_activity_at > RESET_PROJECT_ACTIVITY_INTERVAL.ago
|
|
|
|
end
|
2017-05-04 01:44:39 +00:00
|
|
|
|
|
|
|
def set_last_repository_updated_at
|
2017-06-21 13:48:12 +00:00
|
|
|
Project.unscoped.where(id: project_id)
|
|
|
|
.update_all(last_repository_updated_at: created_at)
|
2017-05-04 01:44:39 +00:00
|
|
|
end
|
2018-02-23 19:33:16 +00:00
|
|
|
|
2018-03-01 14:42:04 +00:00
|
|
|
def track_user_interacted_projects
|
2018-02-26 15:44:35 +00:00
|
|
|
# Note the call to .available? is due to earlier migrations
|
|
|
|
# that would otherwise conflict with the call to .track
|
|
|
|
# (because the table does not exist yet).
|
2018-03-03 19:00:05 +00:00
|
|
|
UserInteractedProject.track(self) if UserInteractedProject.available?
|
2018-02-23 19:33:16 +00:00
|
|
|
end
|
2012-02-28 13:09:23 +00:00
|
|
|
end
|