- 21 Jul, 2015 9 commits
-
-
Valery Sizov authored
This reverts commit fbdaf0e2.
-
Jacob Vosmaer authored
The existing behavior of the backups is to overwrite whatever data was still there in the scratch directories. This broke when we added a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz' already exists. Doing 'rm -f database.sql.gz' before the 'gzip' avoids this failure.
-
Dmitriy Zaporozhets authored
-
Valery Sizov authored
-
Stan Hu authored
Closes #2009
-
Robert Speicher authored
Closes #2001
-
Valery Sizov authored
-
Stan Hu authored
Recalculating graph_log took minutes on a large repository since each of the 6000 commits would need to calculate the diff. Since graph_log does not appear to be used, remove it from the list of things to update. For the Linux kernel repository, this reduced the ProjectCacheWorker time from 8+ minutes to 16 seconds. Closes #2016
-
Valery Sizov authored
This reverts commit ebb6393d.
-
- 19 Jul, 2015 5 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
Fixes from master to 7.13.rc3 See merge request !1001
-
Valery Sizov authored
This reverts commit 94c2516a, reversing changes made to ae44e5ec.
-
Stan Hu authored
Closes #2008
-
Stan Hu authored
Closes #2002
-
- 17 Jul, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
Merge branch 'advanced-cache' into 'master' Backport to stable from merge request !986 - - - Advanced cache Fixes #1993 * Build missing cache values in background job after each push * Store commit_count in project table. Refresh in background job * moved repository size calculation in background job ## Advantages Every time push is triggered - we build cache for project even without user visiting project page. That means first visit is as fast as others now. This is especially good for active projects where people have some requests fast because of cache and some slow - because cache was build in their request. Between cache expired and cache built we we had gap when Linux repo can give 502 error because calculation commits count takes 30 seconds or even more. Using value from database fix this problem. Before cache is updated you see old value from database. After - you see new one. Basically this merge request is super win to GitLab. We don't do some heavy operations in user request but instead in background job. ## Temporary problem After this migration all projects will have `0` commits in database. It fill be replaced with real value on next push. I did not add recalculation to migration because it will last forever on big instances. Can be fixed by adding rake task which will go in background on live instance without downtime See merge request !989
-
Dmitriy Zaporozhets authored
Advanced cache Fixes #1993 * Build missing cache values in background job after each push * Store commit_count in project table. Refresh in background job * moved repository size calculation in background job ## Advantages Every time push is triggered - we build cache for project even without user visiting project page. That means first visit is as fast as others now. This is especially good for active projects where people have some requests fast because of cache and some slow - because cache was build in their request. Between cache expired and cache built we we had gap when Linux repo can give 502 error because calculation commits count takes 30 seconds or even more. Using value from database fix this problem. Before cache is updated you see old value from database. After - you see new one. Basically this merge request is super win to GitLab. We don't do some heavy operations in user request but instead in background job. ## Temporary problem After this migration all projects will have `0` commits in database. It fill be replaced with real value on next push. I did not add recalculation to migration because it will last forever on big instances. Can be fixed by adding rake task which will go in background on live instance without downtime See merge request !986
-
- 15 Jul, 2015 7 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
Time ago fix for compare page See merge request !1905
-
Valery Sizov authored
-
Valery Sizov authored
7-13 stable: changelog update See merge request !1901
-
Valery Sizov authored
-
Sytse Sijbrandij authored
-
Sytse Sijbrandij authored
This reverts commit 8a01a122.
-
- 14 Jul, 2015 17 commits
-
-
Valery Sizov authored
-
Job van der Voort authored
fixed notifications title I fixed the title and link to this document because I believe that it's more clear and easier to find if it has "emails" in the name. See merge request !1897
-
Dmitriy Zaporozhets authored
Fix path to move_drop_indexes.ed Small documentation fix. See merge request !1900
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Add nice scroll for sidebar Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> See merge request !978
-
Dmitriy Zaporozhets authored
Hide scrollbar from sidebar when external mouse is connected to OSX See merge request !977
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Valery Sizov authored
create update guides for 7.13 See merge request !1899
-
Kamil Trzcinski authored
-
Jacob Vosmaer authored
-
Job van der Voort authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Move coverage-related setup back to spec_helper These tools must be loaded before our regular Rails environment. Partially reverts 57830201 See merge request !976
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Add 'ed' step to mysql-to-postgres procedure This change brings the documentation in this repo up to date with that in https://github.com/gitlabhq/mysql-postgresql-converter . See merge request !1896
-
Dmitriy Zaporozhets authored
Fix mentions not being created upon issue/merge request update New cross-references weren't being added when they were made in an issue or merge request update. This happened because the relevant `UpdateService`s were making the `notice_added_references` call after the model had already been updated and saved, so the `changes` attribute was empty and no cross-references were made at all. This fixes the bug and adds a bit of testing and a bit of refactoring. Closes #1773 See merge request !974
-
Dmitriy Zaporozhets authored
Allow user to specify content he wants to see on project page Improvement to !938. Since a lot of people complain on fact they don't like to see README. Especially since we already have a switcher for dashboard - it kind of acceptable to select behaviour. User can specify which content he/she wants to see: ![Screenshot_2015-07-13_18.24.31](https://gitlab.com/gitlab-org/gitlab-ce/uploads/d237474e8f52df4a62ba7e951fa28bd8/Screenshot_2015-07-13_18.24.31.png) ![Screenshot_2015-07-13_18.24.36](https://gitlab.com/gitlab-org/gitlab-ce/uploads/473b0e2a94b3de16d048b8332b539816/Screenshot_2015-07-13_18.24.36.png) cc @JobV @jacobvosmaer @marin @sytses See merge request !970
-