An error occurred fetching the project authors.
- 03 May, 2018 2 commits
-
-
Dylan Griffith authored
-
Dylan Griffith authored
-
- 02 May, 2018 2 commits
-
-
Dylan Griffith authored
-
Dylan Griffith authored
-
- 30 Apr, 2018 3 commits
-
-
Dylan Griffith authored
-
Dylan Griffith authored
-
Dylan Griffith authored
Per discussion in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9646#note_65730532 this logic is being optimized elsewhere and it will simplify things if we make less changes to this code right now.
-
- 27 Apr, 2018 1 commit
-
-
Dylan Griffith authored
Rename `runner.belonging_to_group(project.id) -> runner.belonging_to_parent_group_of_project(project.id)`
-
- 23 Apr, 2018 15 commits
-
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
don't differentiate between the different runner types, instead we rely on the Runner model to provide the available projects. scheduling is now applied to all runners equally.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
instead of having the explicit logic duplicated from the scope we can use the scope instead.
-
Alexis Reigel authored
the scope `Ci::Runner.belonging_to_group` does not filter out the runners where the projects has `#group_runners_enabled` set to false anymore. it didn't show up in the runners UI anymore when group runners were disabled. this was confusing. the flag is only relevant when selecting appropriate runner for a build.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
as we're using UNION now we can use INNER JOIN.
-
Alexis Reigel authored
the unions performs much better than the joins, and the execution time is constant with a growing number of records.
-
Alexis Reigel authored
-
- 18 Apr, 2018 1 commit
-
-
Yorick Peterse authored
This reverts the addition of the "goldiloader" Gem and all use of it. While this Gem is very promising it's causing a variety of problems on GitLab.com due to it eager-loading too much data in places where we don't expect/can handle this. At least for the time being this means we have to go back to manually fixing N+1 query problems, but at least those should not cause a negative impact on availability.
-
- 09 Apr, 2018 1 commit
-
-
Sean McGivern authored
Goldiloader is great, but has several issues with has_many :through relations: * https://github.com/salsify/goldiloader/issues/12 * https://github.com/salsify/goldiloader/issues/14 * https://github.com/salsify/goldiloader/issues/18 Rather than try to figure out which applies in each case, we should just do the drudge work of manually disabling autoloading for all relations of this type. We can always use regular preloading for specific cases, but this way we avoid generating invalid queries through Goldiloader's magic.
-
- 28 Mar, 2018 9 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 14 Mar, 2018 1 commit
-
-
Grzegorz Bizon authored
-
- 28 Feb, 2018 1 commit
-
-
Dylan Griffith authored
-
- 05 Feb, 2018 3 commits
-
-
Matija Čupić authored
-
Matija Čupić authored
-
Matija Čupić authored
-
- 04 Feb, 2018 1 commit
-
-
Matija Čupić authored
-