BigW Consortium Gitlab

  1. 11 Aug, 2017 1 commit
  2. 02 Aug, 2017 1 commit
  3. 01 Aug, 2017 1 commit
  4. 20 Jul, 2017 1 commit
  5. 18 Jul, 2017 1 commit
  6. 12 Jun, 2017 1 commit
  7. 08 Jun, 2017 2 commits
    • Bring in security changes from the 9.2.5 release · 565ead61
      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
    • Bring in security changes from the 9.2.5 release · 1d1363e2
      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
  8. 07 Jun, 2017 1 commit
  9. 06 Jun, 2017 1 commit
    • Set artifact working directory to be in the destination store to prevent unnecessary I/O · 8a417f5a
      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
  10. 05 Jun, 2017 1 commit
    • Fix LFS timeouts when trying to save large files · 37dd0737
      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
  11. 01 Jun, 2017 1 commit
  12. 31 May, 2017 1 commit
  13. 02 May, 2017 1 commit
  14. 06 Mar, 2017 2 commits
  15. 24 Feb, 2017 1 commit
    • Minor refactoring of Uploaders · a8c62dfe
      Robert Speicher authored
      - Moves a duplicate `file_storage?` definition into the common
        `GitlabUploader` ancestor.
      - Get the `uploads` base directory from a class method rather than
        hard-coding it where it's needed. This will be used in a subsequent MR
        to store Uploads in the database.
      - Improves the specs for uploaders.
  16. 03 Jan, 2017 2 commits
  17. 15 Dec, 2016 1 commit
  18. 20 Jul, 2016 1 commit
  19. 19 Jul, 2016 1 commit