- 02 10月, 2017 1 次提交
-
-
由 Stan Hu 提交于
Because of a change in GitLab 9.5.4 to prevent users from assuming control of a repository already on disk, the import task broke. Imports would fail with the message, "There is already a repository with that name on disk". This change skips the validation when the import is done from the command-line. Closes #37682
-
- 30 9月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 28 9月, 2017 1 次提交
-
-
由 Gabriel Mazetto 提交于
-
- 20 9月, 2017 1 次提交
-
-
由 Valery Sizov 提交于
It should be deleted from EE side when doing CE->EE merge!
-
- 14 9月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This adds Project#latest_successful_pipeline_for and Project#latest_successful_pipeline_for_default_branch. The 2nd method memoizes the result (taking nil values into account) to ensure the underlying query isn't executed multiple times when viewing a project's homepage. See https://gitlab.com/gitlab-org/gitlab-ce/issues/36878#note_40073607 for more information.
-
- 07 9月, 2017 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
- 06 9月, 2017 1 次提交
-
-
由 Rubén Dávila 提交于
The following optimizations were performed: - Add new association to GroupMember and ProjectMember This new association will allow us to check if a user is a member of a Project or Group through a single query instead of two. - Optimize retrieving of Members when adding multiple Users
-
- 04 9月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 31 8月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
In this instance its subgroups, and given we can't deploy it, we shouldn't allow it to be shown. Fixes gitlab-org/gitlab-ce#34864
-
- 28 8月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 26 8月, 2017 1 次提交
-
-
由 Gabriel Mazetto 提交于
There are some redundancies in the validation steps, and that is to preserve current error messages behavior Also few specs have to be changed in order to fix madness in validation logic.
-
- 24 8月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 23 8月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 22 8月, 2017 7 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
Using `extend` dynamically can lead to bad performance as it invalidates the method's cache.
-
由 Gabriel Mazetto 提交于
-
- 17 8月, 2017 3 次提交
-
-
由 Tiago Botelho 提交于
Backports EE mirror stuck handling feature (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2628) to CE
-
由 Nick Thomas 提交于
-
由 Nick Thomas 提交于
-
- 15 8月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
The number of forks of a project doesn't change very frequently and running a COUNT(*) every time this information is requested can be quite expensive. We also end up running such a COUNT(*) query at least twice on the homepage of a project. By caching this data and refreshing it when necessary we can reduce project homepage loading times by around 60 milliseconds (based on the timings of https://gitlab.com/gitlab-org/gitlab-ce).
-
- 11 8月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 10 8月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
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.
-
- 09 8月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 08 8月, 2017 1 次提交
-
-
由 blackst0ne 提交于
-
- 03 8月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 02 8月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 01 8月, 2017 2 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
- 29 7月, 2017 1 次提交
-
-
由 Michael Kozono 提交于
-
- 27 7月, 2017 2 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 24 7月, 2017 1 次提交
-
-
由 Jarka Kadlecova 提交于
-
- 20 7月, 2017 1 次提交
-
-
由 Alexander Randa 提交于
-
- 18 7月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 13 7月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-