1. 29 Apr, 2019 1 commit
  2. 23 Apr, 2019 1 commit
    • Kamil Trzciński's avatar
      Merge branch... · 4adcfd43
      Kamil Trzciński authored
      Merge branch '60500-disable-jit-kubernetes-resource-creation-for-project-level-clusters' into 'master'
      
      Disable JIT Kubernetes resource creation for project level clusters
      
      Closes #60500
      
      See merge request gitlab-org/gitlab-ce!27352
      
      (cherry picked from commit a6a1afe0)
      
      e33ecfde Disable JIT resource creation for project clusters
      4adcfd43
  3. 12 Apr, 2019 2 commits
  4. 01 Apr, 2019 1 commit
  5. 27 Mar, 2019 1 commit
    • Nick Thomas's avatar
      Allow external diffs to be used conditionally · 0e831b0b
      Nick Thomas authored
      Since external diffs are likely to be a bit slower than in-database
      ones, add a mode that makes diffs external after they've been obsoleted
      by events. This should strike a balance between performance and disk
      space.
      
      A background cron drives the majority of migrations, since diffs become
      outdated through user actions.
      0e831b0b
  6. 25 Mar, 2019 2 commits
  7. 20 Mar, 2019 2 commits
    • Tiger's avatar
      Add feature flag for build preparing state · 759dab5b
      Tiger authored
      The flag is on by default, but allows us to revert back
      to the old behaviour if we encounter any problems.
      759dab5b
    • Tiger's avatar
      Create framework for build prerequisites · 00f0d356
      Tiger authored
      Introduces the concept of Prerequisites for a CI build.
      If a build has unmet prerequisites it will go through the
      :preparing state before being made available to a runner.
      
      There are no actual prerequisites yet, so current
      behaviour is unchanged.
      00f0d356
  8. 04 Mar, 2019 1 commit
  9. 01 Mar, 2019 4 commits
  10. 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.
      5ae9a44a
  11. 20 Feb, 2019 1 commit
  12. 07 Feb, 2019 1 commit
    • Stan Hu's avatar
      Fix failing test in spec/workers/post_receive_spec.rb · 28c48804
      Stan Hu authored
      This is what was happening before:
      
      1. `Project#set_timestamps_for_create` was called at creation time
      and set the `last_activity_at` and `last_repository_updated_at`
      to the current timestamp T.
      
      2. The test ran `PostReceive#perform`, which then called
      `PostReceive#process_wiki_changes`. If less than 500 milliseconds
      elapsed since T, then the update would just set the timestamp to T.
      
      To fix this problem, we can just use Timecop to ensure at least
      one second has elapsed after attempting to process changes.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/8871
      28c48804
  13. 06 Feb, 2019 2 commits
  14. 05 Feb, 2019 1 commit
  15. 25 Jan, 2019 4 commits
    • Gabriel Mazetto's avatar
      Refactor Storage Migration · 7bc16889
      Gabriel Mazetto authored
      Specs were reviewed and improved to better cover the current behavior.
      There was some standardization done as well to facilitate the
      implementation of the rollback functionality.
      
      StorageMigratorWorker was extracted to HashedStorage namespace were
      RollbackerWorker will live one as well.
      7bc16889
    • Gabriel Mazetto's avatar
      Move MigrationService to HashedStorage module · cf52488c
      Gabriel Mazetto authored
      This is part of the refactor to include a RollbackService into
      HashedStorage module
      cf52488c
    • Gabriel Mazetto's avatar
      Prepare rake task for storage rollback · c2c34eba
      Gabriel Mazetto authored
      We are keeping compatibility with existing scheduled jobs.
      c2c34eba
    • Kamil Trzciński's avatar
      Add Container Registry API · 045d07ba
      Kamil Trzciński authored
      This includes a set of APIs to manipulate container registry.
      This includes also an ability to delete tags based on requested
      criteria, like keep-last-n, matching-name, older-than.
      045d07ba
  16. 24 Jan, 2019 2 commits
  17. 15 Jan, 2019 1 commit
    • Stan Hu's avatar
      Only send one notification for failed remote mirror · 6fbbd4ab
      Stan Hu authored
      Retries in Sidekiq and in the remote mirror scheduler can cause repeated
      attempts in quick succession if the sync fails. Each failure will then
      send an e-mail to all project maintainers, which can spam users
      unnecessarily.
      
      Modify the logic to send one notification the first time the mirror
      fails by setting `error_notification_sent` to `true` and reset the
      flag after a successful sync.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56222
      6fbbd4ab
  18. 14 Jan, 2019 1 commit
    • Zeger-Jan van de Weg's avatar
      Ensure pool participants are linked before GC · e03602e0
      Zeger-Jan van de Weg authored
      In theory the case could happen that the initial linking of the pool
      fails and so do all the retries that Sidekiq performs. This could lead
      to data loss.
      
      To prevent that case, linking is done before Gits GC too. This makes
      sure that case doesn't happen.
      e03602e0
  19. 07 Jan, 2019 1 commit
  20. 04 Jan, 2019 1 commit
  21. 21 Dec, 2018 2 commits
  22. 19 Dec, 2018 1 commit
  23. 18 Dec, 2018 1 commit
  24. 12 Dec, 2018 1 commit
  25. 07 Dec, 2018 3 commits
    • Zeger-Jan van de Weg's avatar
      Allow public forks to be deduplicated · 896c0bdb
      Zeger-Jan van de Weg authored
      When a project is forked, the new repository used to be a deep copy of everything
      stored on disk by leveraging `git clone`. This works well, and makes isolation
      between repository easy. However, the clone is at the start 100% the same as the
      origin repository. And in the case of the objects in the object directory, this
      is almost always going to be a lot of duplication.
      
      Object Pools are a way to create a third repository that essentially only exists
      for its 'objects' subdirectory. This third repository's object directory will be
      set as alternate location for objects. This means that in the case an object is
      missing in the local repository, git will look in another location. This other
      location is the object pool repository.
      
      When Git performs garbage collection, it's smart enough to check the
      alternate location. When objects are duplicated, it will allow git to
      throw one copy away. This copy is on the local repository, where to pool
      remains as is.
      
      These pools have an origin location, which for now will always be a
      repository that itself is not a fork. When the root of a fork network is
      forked by a user, the fork still clones the full repository. Async, the
      pool repository will be created.
      
      Either one of these processes can be done earlier than the other. To
      handle this race condition, the Join ObjectPool operation is
      idempotent. Given its idempotent, we can schedule it twice, with the
      same effect.
      
      To accommodate the holding of state two migrations have been added.
      1. Added a state column to the pool_repositories column. This column is
      managed by the state machine, allowing for hooks on transitions.
      2. pool_repositories now has a source_project_id. This column in
      convenient to have for multiple reasons: it has a unique index allowing
      the database to handle race conditions when creating a new record. Also,
      it's nice to know who the host is. As that's a short link to the fork
      networks root.
      
      Object pools are only available for public project, which use hashed
      storage and when forking from the root of the fork network. (That is,
      the project being forked from itself isn't a fork)
      
      In this commit message I use both ObjectPool and Pool repositories,
      which are alike, but different from each other. ObjectPool refers to
      whatever is on the disk stored and managed by Gitaly. PoolRepository is
      the record in the database.
      896c0bdb
    • Douwe Maan's avatar
      Improve PruneWebHookLogsWorker spec · d5094e7c
      Douwe Maan authored
      d5094e7c
    • Douwe Maan's avatar
      Remove RemoveOldWebHookLogsWorker · 536c1e40
      Douwe Maan authored
      536c1e40
  26. 06 Dec, 2018 1 commit