An error occurred fetching the project authors.
- 19 Sep, 2017 1 commit
-
-
Andrew Newdigate authored
-
- 16 Sep, 2017 1 commit
-
-
Vitaliy @blackst0ne Klachkov authored
-
- 11 Sep, 2017 1 commit
-
-
Annabel Dunstone Gray authored
This reverts merge request !14148
-
- 08 Sep, 2017 1 commit
-
-
Rubén Dávila authored
Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'" This reverts merge request !13619
-
- 06 Sep, 2017 7 commits
-
-
blackst0ne authored
-
Rubén Dávila authored
-
Yorick Peterse authored
This finishes the procedure for migrating events from the old format into the new format. Code no longer uses the old setup and the database tables used during the migration process are swapped, with the old table being dropped. While the database migration can be reversed this will 1) take a lot of time as data has to be coped around 2) won't restore data in the "events.data" column as we have no way of restoring this. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
-
micael.bergeron authored
-
micael.bergeron authored
-
Ashley Dumaine authored
-
Ashley Dumaine authored
-
- 05 Sep, 2017 1 commit
-
-
Robert Schilling authored
-
- 04 Sep, 2017 3 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 03 Sep, 2017 1 commit
-
-
Shinya Maeda authored
-
- 30 Aug, 2017 2 commits
-
-
Nick Thomas authored
`allowed_key_types` is removed and the `minimum_<type>_bits` fields are renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies that the key type is disabled. This also feeds through to the UI - checkboxes per key type are out, inline selection of "forbidden" and "allowed" (i.e., no restrictions) are in. As with the previous model, unknown key types are disallowed, even if the underlying ssh daemon happens to support them. The defaults have also been changed from the lowest known bit size to "no restriction". So if someone does happen to have a 768-bit RSA key, it will continue to work on upgrade, at least until the administrator restricts them.
-
Nick Thomas authored
This is an amalgamation of: * Cory Hinshaw: Initial implementation !5552 * Rémy Coutable: Updates !9350 * Nick Thomas: Resolve conflicts and add ED25519 support !13712
-
- 29 Aug, 2017 2 commits
-
-
Travis Miller authored
-
Travis Miller authored
-
- 15 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 14 Aug, 2017 1 commit
-
-
Robert Speicher authored
An upcoming update to rubocop-gitlab-security added additional violations.
-
- 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.
-
- 09 Aug, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 08 Aug, 2017 2 commits
-
-
sue445 authored
-
Rémy Coutable authored
Fix the /projects/:id/repository/tags endpoint to handle dots in the tag name when the project full path contains a `/` Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 04 Aug, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 03 Aug, 2017 1 commit
-
-
Tony authored
-
- 02 Aug, 2017 2 commits
- 27 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 25 Jul, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 24 Jul, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 21 Jul, 2017 2 commits
-
-
Douwe Maan authored
-
Felipe Artur authored
-
- 13 Jul, 2017 1 commit
-
-
Robin Bobbitt authored
When sign-in is disabled: - skip password expiration checks - prevent password reset requests - don’t show Password tab in User Settings - don’t allow login with username/password for Git over HTTP requests - render 404 on requests to Profiles::PasswordsController
-
- 11 Jul, 2017 1 commit
-
-
Stan Hu authored
The current "basic" merge request API still loads too much data. For integrations like the Trello Power-up, we just need the basics. Closes #34920
-
- 09 Jul, 2017 1 commit
-
-
Stan Hu authored
Closes #34159
-
- 07 Jul, 2017 2 commits
-
-
Felipe Artur authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-