Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-03-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2023-03-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2023-02-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2023-02-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2023-01-20Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-12-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-12-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-06-21Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-06-11Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-05-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-03-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-03-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-02-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-10-20Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-10-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-08-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-06-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-05-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-07-26Add frozen_string_literal to spec/featuresThong Kuah
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2018-11-20Resolve "Further UI improvements to Profile "Overview" tab"Martin Wortschack
2018-11-06Resolve "Redesign activity feed"Martin Wortschack
2018-10-04Resolve "Add new "Overview" tab on user profile page"Martin Wortschack
2018-07-05Enable Capybara/FeatureMethods copWinnie Hellmann
2017-12-19fixed specs and the non-rendering stat_graph_contributors_graphJose Ivan Vargas
2017-11-02add visible argument to helper rather than duplicating codeMike Greiling
2017-10-30fix page render issues on contribution calendar while tests are runMike Greiling
2017-08-24Delegate Repository::branch_exists? and ref_exists? to Gitlab::GitAndrew Newdigate
2017-08-10Migrate events into a new formatYorick 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.
2017-08-03Change all `:empty_project` to `:project`Robert Speicher
2017-07-27Remove superfluous type defs in specsKeifer Furzland
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-06-29Change gitlab_sign_in to sign_in where possibleRobert Speicher
2017-06-20Change `login_as` uses to `gitlab_sign_in`Robert Speicher
2017-05-23Use wait_for_requests to wait all JS requestOswaldo Ferreira
2017-04-24Merge branch 'jacopo-beschi/gitlab-ce-29712-unnecessary-wait-for-ajax'Rémy Coutable
See merge request !10567 Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-04-21Unnecessary "include WaitForAjax" and "include ApiHelpers"Jacopo
Removed all the unnecessary include of `WaitForAjax` and `ApiHelpers` in the specs. Removed unnecessary usage of `api:true`
2017-04-21Use `:empty_project` where possible in top-level feature specsRobert Speicher
2017-02-13Add comment events to contributions calendarRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-11-04Fix deselecting calendar days on contribution graphClement Ho
2016-10-01Changed zero padded days to no padded days in date_formatClement Ho
2016-09-26Add more tests for calendar contributionClement Ho
2016-09-16Replace contributions calendar timezone payload with datesClement Ho