- 04 Sep, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 31 Aug, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 28 Aug, 2017 1 commit
-
-
James Lopez authored
-
- 22 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 21 Aug, 2017 1 commit
-
-
James Lopez authored
-
- 10 Aug, 2017 1 commit
-
-
Yorick Peterse authored
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.
-
- 07 Aug, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 06 Jul, 2017 1 commit
-
-
Sean McGivern authored
This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
-
- 05 Jul, 2017 4 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 26 Jun, 2017 1 commit
-
-
Adam Niedzielski authored
Closes #34052
-
- 16 Jun, 2017 1 commit
-
-
Sean McGivern authored
This adds an ID-less table containing one row per file, per merge request diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised currently, with the advantage that we can easily query the attributes of this new table. It does not migrate existing data, so we have fallback code when the legacy st_diffs column is present instead. For a merge request diff to be valid, it should have at most one of: * Rows in this new table, with the correct merge_request_diff_id. * A non-NULL st_diffs column. It may have neither, if the diff is empty.
-
- 05 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 07 May, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 05 May, 2017 1 commit
-
-
James Lopez authored
-
- 03 May, 2017 2 commits
-
-
James Lopez authored
-
James Lopez authored
-
- 02 May, 2017 1 commit
-
-
James Lopez authored
-
- 06 Apr, 2017 4 commits
-
-
Kamil Trzcinski authored
-
Lin Jen-Shin authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 04 Apr, 2017 3 commits
-
-
James Lopez authored
-
James Edwards-Jones authored
-
James Edwards-Jones authored
-
- 17 Mar, 2017 1 commit
-
-
Kamil Trzciński authored
-
- 30 Jan, 2017 1 commit
-
-
James Lopez authored
* Regenerates tokens for all models that have them * Remove variables, since they are basically just storing encrypted data * Bumped version up to 0.1.6 * Updated related docs
-
- 15 Jan, 2017 1 commit
-
-
Ruben Davila authored
-
- 19 Oct, 2016 4 commits
-
-
James Lopez authored
Fixed all related specs and also changed the logic to handle edge cases. This includes exporting and exporting of group labels, which will get associated with the new group (if any) or they will become normal project labels otherwise. Found other issues to do with not being able to import all labels at once in the beginning of the JSON - code was much simpler when we import all labels and milestones associated to a project first, then the associations will find the already created labels instead of creating them from the associations themselves.
-
James Lopez authored
-
James Lopez authored
-
Douglas Barbosa Alexandre authored
-
- 27 Sep, 2016 1 commit
-
-
James Lopez authored
-
- 26 Sep, 2016 1 commit
-
-
James Lopez authored
Fixes issue with rails reserved keyword type exporting/importing services. Also fixed CustomIssueTrackerService title setter and added relevant specs.
-
- 21 Sep, 2016 1 commit
-
-
James Lopez authored
-
- 19 Sep, 2016 1 commit
-
-
James Lopez authored
Better import of labels, milestones and protected branches. Updated relevant specs. Loose pipeline validation on importing, so it does not fail when there are missing fields, which are not validated at DB level. Also, updated spec with relevant test.
-
- 01 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 01 Aug, 2016 1 commit
-
-
James Lopez authored
squashed - fixed label and milestone association problems, updated specs and refactored reader class a bit
-