1. 03 Oct, 2018 1 commit
  2. 05 Jul, 2018 1 commit
  3. 05 Apr, 2018 1 commit
  4. 28 Feb, 2018 3 commits
  5. 03 Feb, 2018 1 commit
  6. 01 Feb, 2018 1 commit
  7. 17 Jan, 2018 2 commits
    • Micaël Bergeron's avatar
      fix the artifact/lfs specs · 913df61d
      Micaël Bergeron authored
      913df61d
    • Micaël Bergeron's avatar
      Refactor the uploaders · 594e6a0a
      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.
      594e6a0a
  8. 06 Dec, 2017 1 commit
  9. 03 Dec, 2017 5 commits
  10. 07 Sep, 2017 1 commit
  11. 07 Jun, 2017 3 commits
  12. 06 Jun, 2017 1 commit
  13. 01 Jun, 2017 2 commits
  14. 02 May, 2017 1 commit
  15. 24 Feb, 2017 1 commit
    • Robert Speicher's avatar
      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.
      a8c62dfe
  16. 15 Dec, 2016 1 commit
  17. 24 Jul, 2016 1 commit
  18. 14 Jan, 2016 1 commit
  19. 29 Dec, 2015 1 commit
    • Grzegorz Bizon's avatar
      Add hotfix that allows to access build artifacts created before 8.3 · 50469645
      Grzegorz Bizon authored
      This is a temporary hotfix that allows to access build artifacts created
      before 8.3. See #5257.
      
      This needs to be changed after migrating CI build files.
      
      Note that `ArtifactUploader` uses `artifacts_path` to create a storage
      directory before and after parsisting `Ci::Build` instance, before and
      after moving a file to store (save and fetch a file).
      50469645
  20. 18 Dec, 2015 1 commit
    • Kamil Trzciński's avatar
      Add GitLab Pages · 650d6a63
      Kamil Trzciński authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under: http://group.pages.domain.com/project
      - Pages can be used to serve the group page, special project named as host: group.pages.domain.com
      - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
      - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
      - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
      - The public/ is extracted from artifacts and content is served as static pages
      - Pages asynchronous worker use `dd` to limit the unpacked tar size
      - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
      - Pages are part of backups
      - Pages notify the deployment status using Commit Status API
      - Pages use a new sidekiq queue: pages
      - Pages use a separate nginx config which needs to be explicitly added
      650d6a63
  21. 23 Nov, 2015 1 commit
  22. 10 Nov, 2015 2 commits