GitLab steht aufgrund wichtiger Wartungsarbeiten am Montag, den 8. März, zwischen 17:00 und 19:00 Uhr nicht zur Verfügung.

  1. 02 Apr, 2019 1 commit
  2. 20 Mar, 2019 1 commit
  3. 06 Mar, 2019 1 commit
  4. 05 Mar, 2019 1 commit
    • Gabriel Mazetto's avatar
      Skip project validation when switching storage layouts · b4f20502
      Gabriel Mazetto authored
      This is a fix for the Hashed Storage migration and Rollback procedure
      to ignore any project-level validation error that can happen in a
      long-running instance.
      There are many situations where defaults and acceptable values changed
      but, because we didn't provide a migration to "valid" attributes, it
      can happen that project will not be `valid? => true`.
      Because the changes we are making are limited to setting a project as
      read_only or changing the storage_level, it's safe to bypass validation.
  5. 01 Mar, 2019 8 commits
  6. 27 Feb, 2019 1 commit
    • Jacopo's avatar
      Add project http fetch statistics API · 5ae9a44a
      Jacopo authored
      The API get projects/:id/traffic/fetches allows user with write
      access to the repository to get the number of clones for the
      last 30 days.
  7. 20 Feb, 2019 1 commit
  8. 19 Feb, 2019 1 commit
  9. 06 Feb, 2019 2 commits
  10. 31 Jan, 2019 3 commits
  11. 25 Jan, 2019 6 commits
  12. 22 Jan, 2019 2 commits
    • Kamil Trzciński's avatar
      Extract GitLab Pages using RubyZip · 1a8100cf
      Kamil Trzciński authored
      RubyZip allows us to perform strong validation of
      expanded paths where we do extract file.
      We introduce the following additional checks
      to extract routines:
      1. None of path components can be symlinked,
      2. We drop privileges support for directories,
      3. Symlink source needs to point within the target directory,
         like `public/`,
      4. The symlink source needs to exist ahead of time.
    • Gabriel Mazetto's avatar
      Refactored AfterRenameService to reduce coupling · d391dfb4
      Gabriel Mazetto authored
      We still rely on the Dirty API for project rename (before/after) values,
      but we don't access the dirty api from the service class anymore.
      The previous value is now part of the initialization, which makes it
      easier to test and the behavior is clearer.
      The same was done with the `rename_repo` on the Storage classes, we now
      provide before and after values as part of the method signature.
  13. 21 Jan, 2019 2 commits
    • Gabriel Mazetto's avatar
      Fixed legacy storage renaming code · 7a7948e6
      Gabriel Mazetto authored
      During a previous refactor on project model, code related to the
      hashed storage was extracted into AfterRenameService, see
      The "path_before" was changed from using `previous_changes['path']` to
      `path_was`. They are not equivalent. `path_was` exists reliably only
      *before* persisting to the database. After database persistence is
      confirmed, the value is moved to `previous_changes[:attribute_name]`.
      Because the repository/attachments rename or storage upgrade happens
      after it was persisted to the database, we were in fact not informing
      the right parameters (and therefore not doing what it was supposed to).
    • Francisco Javier López's avatar
  14. 18 Jan, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Cleanup stale +deleted repo paths on project removal · 4fd848fc
      Oswaldo Ferreira authored
      1. When removing projects, we can end-up leaving the +deleted
      repo path dirty and not successfully removing the non-deleted
      namespace (mv process is not atomic and can be killed without
      fully moving the path).
      2. In order to solve that, we're adding a clean-up phase on
      ensure which will schedule possible staled +deleted path deletion.
      Note that we don't check the current state (if there is or not a
      repo) in order to schedule the deletion. That's intentional
      in order to leverage Gitlab::GitalyClient::NamespaceService#remove
      idempotency and ensure consistency.
  15. 16 Jan, 2019 4 commits
  16. 11 Jan, 2019 1 commit
  17. 07 Jan, 2019 3 commits
  18. 06 Jan, 2019 1 commit