- 22 Feb, 2018 1 commit
-
-
Sean McGivern authored
-
- 06 Feb, 2018 7 commits
-
-
Micaël Bergeron authored
it will also automatically prune empty directories for `FileUploader`-based uploaders.
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 02 Feb, 2018 2 commits
-
-
Micaël Bergeron authored
-
Micaël Bergeron authored
-
- 01 Feb, 2018 3 commits
-
-
Micaël Bergeron authored
-
Micaël Bergeron authored
-
Micaël Bergeron authored
-
- 07 Dec, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 03 Dec, 2017 8 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
Kamil Trzcinski 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.
-
- 28 Nov, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 21 Nov, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 30 Oct, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 19 Sep, 2017 1 commit
-
-
Kamil Trzcinski authored
Instead perform soft check (the column set to indicate that file does exist)
-
- 11 Aug, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 01 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 20 Jul, 2017 1 commit
-
-
Sean McGivern authored
Use uploads/system directory for personal snippets See merge request !2123
-
- 18 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 12 Jun, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 08 Jun, 2017 3 commits
-
-
Bob Van Landuyt authored
-
DJ Mountney authored
Ran: - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch - git checkout -b 9-2-5-security-patch origin/v9.2.2 - git apply patchfile.patch - git commit - [Got the sha ref for the commit] - git checkout -b upstream-9-2-security master - git cherry-pick <SHA of the patchfile commit> - [Resolved conflicts] - git cherry-pick --continue
-
DJ Mountney authored
Ran: - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch - git checkout -b 9-2-5-security-patch origin/v9.2.2 - git apply patchfile.patch - git commit - [Got the sha ref for the commit] - git checkout -b upstream-9-2-security master - git cherry-pick <SHA of the patchfile commit> - [Resolved conflicts] - git cherry-pick --continue
-
- 07 Jun, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 06 Jun, 2017 1 commit
-
-
Stan Hu authored
Similar to #33218, build artifacts were being uploaded into a CarrierWave temporary directory in the Rails root directory before moved to their final destination, which could cause a copy across filesystems. This merge request refactors the work in !11866 so that any uploader can just override `work_dir` to change the default implementation. Closes #33274
-
- 05 Jun, 2017 1 commit
-
-
Stan Hu authored
The following was happening: 1. Workhorse stores an LFS file in /var/opt/gitlab/gitlab-rails/shared/lfs-objects 2. CarrierWave then renames the file to a temporary directory (e.g. /opt/gitlab/embedded/service/gitlab-rails/tmp) 3. CarrierWave then renames the file to its final location (e.g. /var/opt/gitlab/gitlab-rails/shared/lfs-objects) When the LFS upload path was on a different filesystem than the Rails installation, step 2 could take a longer than 10 seconds, at which point Workhorse would time out with "badgateway: failed after 10s: context canceled". This change makes the work path in the same root as the LFS storage path, preventing moves across filesystems. Closes #33218
-
- 01 Jun, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 31 May, 2017 1 commit
-
-
Jarka Kadlecova authored
-