- Feb 08, 2018
-
-
Gregory 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.
-
- Feb 06, 2018
-
-
Shinya Maeda authored
-
Shinya Maeda authored
This reverts commit 3603e7c3a2cfd88e8441c5d76303645776349117.
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- Dec 21, 2017
-
-
Kamil Trzcińśki authored
-
- Dec 14, 2017
-
-
Rémy Coutable authored
I've followed the [upgrade guide](https://github.com/thoughtbot/factory_bot/blob/4-9-0-stable/UPGRADE_FROM_FACTORY_GIRL.md ) and ran these two commands: ``` grep -e FactoryGirl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|FactoryGirl|FactoryBot|" grep -e factory_girl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|factory_girl|factory_bot|" ``` Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Dec 03, 2017
-
-
Kamil Trzcińśki authored
-
Kamil Trzcińśki authored
-
Kamil Trzcińśki authored
-
Kamil Trzcińśki authored
-
Zeger-Jan van de Weg authored
-
Kamil Trzcińśki authored
-
Zeger-Jan van de Weg authored
Two things at ones, as there was no clean way to seperate the commit and give me feedback from the tests. But the model Artifact is now JobArtifact, and the table does not have a type anymore, but the metadata is now its own model: Ci::JobArtifactMetadata.
-
Zeger-Jan van de Weg authored
To allow jobs/builds to have multiple artifacts, and to start seperating concerns from Ci::Build a new model is created: Ci::Artifact. Changes include the updating of the ArtifactUploader to adapt to a slightly different interface. The uploader expects to be initialized with a `Ci::Build`. Futher a migration with the minimal fields, the needed foreign keys and an index. Last, the way this works is by prepending a module to Ci::Build so we can basically override behaviour but if needed use `super` to get the original behaviour.
-
- Oct 30, 2017
-
-
Zeger-Jan van de Weg authored
Minor annoyance of mine, and there were a couple of things wrong, for example: 1. Switching on a property is just a trait 2. It didn't inherrit from its parent Find and replace through the code based fixed all occurances.
-
- Oct 05, 2017
-
-
Alessio Caiazza authored
-
Grzegorz Bizon authored
-
- Sep 04, 2017
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- Sep 03, 2017
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- Aug 25, 2017
-
-
Lin Jen-Shin authored
And specify owners more clearly
-
- Aug 16, 2017
-
-
Grzegorz Bizon authored
-
- Aug 02, 2017
-
-
Robert Speicher authored
-
- Jul 28, 2017
-
-
Shinya Maeda authored
-
- Jul 20, 2017
-
-
Alexander Randa authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- Jul 17, 2017
-
-
Grzegorz Bizon authored
-