delta/gitlab/gitlab-ce.git, branch update_for_stable

Revert "Merge branch 'cache-improvement' into '7-13-stable' "

2015-07-19T19:49:21+00:00

This reverts commit 94c2516afc7ad8854844c05001f4a390d0bd8724, reversing
changes made to ae44e5ec064aaa9f5063732dc7bb6ee751a80ce2.

Fix bug where notes were being rendered with wrong color preferences due to caching

2015-07-19T19:37:11+00:00

Closes #2008

Fix bug where clicking on the link icon on a file would result in "L#undefined" in the URL

2015-07-19T19:36:14+00:00

Closes #2002

Merge branch 'cache-improvement' into '7-13-stable'

2015-07-17T16:19:50+00:00


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

Merge branch 'advanced-cache' into 'master'

2015-07-17T15:22:13+00:00


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

Version 7.13.0.rc2

2015-07-15T17:13:47+00:00

Merge branch 'update_stable' into '7-13-stable'

2015-07-15T14:42:51+00:00


Time ago fix for compare page



See merge request !1905

Time ago fix for compare page

2015-07-15T14:40:59+00:00

Merge branch '7-13-stable_changelog' into '7-13-stable'

2015-07-15T09:16:19+00:00


7-13 stable: changelog update



See merge request !1901

changelog update

2015-07-15T09:15:32+00:00