An error occurred fetching the project authors.
- 16 Feb, 2018 1 commit
-
-
Stan Hu authored
This reverts merge request !16578
-
- 09 Feb, 2018 4 commits
-
-
Greg Stark authored
-
Greg Stark authored
-
Greg Stark authored
-
Greg Stark authored
-
- 08 Feb, 2018 1 commit
-
-
Greg Stark authored
Artifacts are in the middle of being migrated from ci_builds to ci_job_artifacts. The expiration date is currently visible in both of these tables and the test for whether an expired artifact is present for a job is complex as it requires checking both the of the tables. Add two new indexes, one on ci_builds.artifacts_expire_at and one on ci_job_artifacts.expire_at to enable finding expired artifacts efficiently. And until the migration is finished, replace the SQL for finding expired and non-expired artifacts with a hand-crafted UNION ALL based query instead of using OR. This overcomes a database optimizer limitation that prevents it from using these indexes. When the migration is finished the next version should remove this query and replace it with a much simpler query on just ci_job_artifacts. See https://gitlab.com/gitlab-org/gitlab-ce/issues/42561 for followup.
-
- 07 Feb, 2018 2 commits
-
-
Greg Stark authored
-
Dylan Griffith authored
-
- 06 Feb, 2018 2 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 31 Jan, 2018 2 commits
-
-
Takuya Noguchi authored
-
Takuya Noguchi authored
-
- 26 Jan, 2018 1 commit
-
-
Matija Čupić authored
-
- 17 Jan, 2018 1 commit
-
-
Micaël Bergeron authored
I've demoted the ObjectStoreUploader to a concern that is mixed in the concrete uploader classes that need to store files in a remote object store. I've been working on making the local -> remote migration working first, which has been trivial compared to the remote -> local one. The current implementation is heavily based on side-effects which makes the code brittle and hard to reason about. The current approach is to store the `store` field in the correct `Upload` model once a migration has been done. To retrieve the field I use the `has_many :uploads` relationship, with all the paths that a certain file may have `uploads.where(path: paths).last`. This as the drawback of adding a database query for every upload lookup, but I feel that the generalization of this behavior is worth it. We should be able to optimize this down the road quite easily.
-
- 15 Jan, 2018 1 commit
-
-
Stan Hu authored
This should reduce the number of SQL queries and lookups needed to look up a project of a build and pipeline and vice versa. Before: ``` [1] pry(main)> Ci::Build.reflect_on_association(:project).has_inverse? => false [2] pry(main)> Project.reflect_on_association(:builds).has_inverse? => false [3] pry(main)> Ci::Pipeline.reflect_on_association(:project).has_inverse? => false [4] pry(main)> Project.reflect_on_association(:pipelines).has_inverse? => :project ``` After: ``` [1] pry(main)> Ci::Build.reflect_on_association(:project).has_inverse? => :builds [2] pry(main)> Project.reflect_on_association(:builds).has_inverse? => :project [3] pry(main)> Ci::Pipeline.reflect_on_association(:project).has_inverse? => :pipelines [4] pry(main)> Project.reflect_on_association(:pipelines).has_inverse? => :project ```
-
- 14 Jan, 2018 1 commit
-
-
Stan Hu authored
This should reduce the number of SQL queries and lookups needed to look up a project of a build and pipeline and vice versa. Before: ``` [1] pry(main)> Ci::Build.reflect_on_association(:project).has_inverse? => false [2] pry(main)> Project.reflect_on_association(:builds).has_inverse? => false [3] pry(main)> Ci::Pipeline.reflect_on_association(:project).has_inverse? => false [4] pry(main)> Project.reflect_on_association(:pipelines).has_inverse? => :project ``` After: ``` [1] pry(main)> Ci::Build.reflect_on_association(:project).has_inverse? => :builds [2] pry(main)> Project.reflect_on_association(:builds).has_inverse? => :project [3] pry(main)> Ci::Pipeline.reflect_on_association(:project).has_inverse? => :pipelines [4] pry(main)> Project.reflect_on_association(:pipelines).has_inverse? => :project ```
-
- 05 Jan, 2018 4 commits
-
-
Matija Čupić authored
-
Matija Čupić authored
-
Matija Čupić authored
-
Grzegorz Bizon authored
-
- 04 Jan, 2018 2 commits
-
-
Matija Čupić authored
-
Matija Čupić authored
-
- 22 Dec, 2017 1 commit
-
-
Matija Čupić authored
-
- 14 Dec, 2017 1 commit
-
-
Shinya Maeda authored
-
- 07 Dec, 2017 2 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 06 Dec, 2017 7 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
Use Class.new(StandardError) instead of custom extended error class. Bring back specified_dependencies?.
-
Shinya Maeda authored
-
- 05 Dec, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 03 Dec, 2017 6 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-