- 25 Apr, 2017 1 commit
-
-
Sean McGivern authored
The problem is that we often go via a diff object constructed from the diffs stored in the DB. Those diffs, by definition, don't overflow, so we don't have access to the 'correct' `real_size` - that is stored on the MR diff object iself.
-
- 24 Apr, 2017 6 commits
-
-
Douwe Maan authored
-
Stan Hu authored
We see in #27387 that a call to `polymorphic_path` will cause duplicate SELECT route calls for each merge request in a milestone. This happens because calling `project.namespace.becomes(Namespace)` will instantiate a new instance of a Namespace for each merge request, which causes a N+1 query on the routes table. This change caches the state of the route by the specific class and ID, which dramatically eliminates duplicate work.
-
Toon Claes authored
-
Toon Claes authored
Make it gracefully handle unexisting pipelines and refactor iterating all the merge request paths.
-
Toon Claes authored
And add some specs.
-
Toon Claes authored
Turn ExpirePipelineCacheService into Worker so it can fetch all the merge requests for which the pipeline runs or did run against.
-
- 21 Apr, 2017 5 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Nick Thomas authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Nick Thomas authored
-
- 20 Apr, 2017 1 commit
-
-
Valery Sizov authored
-
- 19 Apr, 2017 1 commit
-
-
James Lopez authored
-
- 18 Apr, 2017 3 commits
-
-
Valery Sizov authored
-
Tiago Botelho authored
-
Stan Hu authored
Before deleting a user via a SpamLog would just call `user.destroy`, which may omit other things that need to be cleaned up.
-
- 17 Apr, 2017 2 commits
-
-
Sean McGivern authored
`git log --follow` is only supported for a single path. CE doesn't currently pass multiple paths, but EE does.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 16 Apr, 2017 1 commit
-
-
Stan Hu authored
In the case of spammers, we really want a hard delete to avoid retaining spam. Closes #31021
-
- 13 Apr, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 12 Apr, 2017 1 commit
-
-
Yorick Peterse authored
Starting with GitLab 9.1.0 we will no longer allow downtime migrations unless absolutely necessary. This commit updates the various developer guides and adds code that is necessary to make zero downtime migrations less painful.
-
- 11 Apr, 2017 4 commits
-
-
blackst0ne authored
-
Alejandro Rodríguez authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
mhasbini authored
-
- 10 Apr, 2017 5 commits
-
-
Robert Speicher authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 09 Apr, 2017 2 commits
-
-
blackst0ne authored
-
blackst0ne authored
-
- 07 Apr, 2017 6 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Jacopo authored
Removed `Milestone#is_empty?` because is not used anymore in the codebase
-
- 06 Apr, 2017 1 commit
-
-
Toon Claes authored
Enable caching in the Etag::Middleware and when a pipeline changes status, expire the cache for the project pipelines path.
-