1. 25 Mar, 2019 1 commit
  2. 05 Mar, 2019 3 commits
    • João Cunha's avatar
      Rename ClusterUpdateAppWorker to ClusterPatchAppWorker · 3bdff7aa
      João Cunha authored
      - This is to avoid colision with EE ClusterUpdateAppWorker
    • João Cunha's avatar
      Creates Clusterss::ApplciationsController update endpoint · f8234d9a
      João Cunha authored
      - Creates new route
      - Creates new controller action
      - Creates call stack:
        Clusterss::ApplciationsController calls -->
        Clusters::Applications::UpdateService calls -->
        Clusters::Applications::ScheduleUpdateService calls -->
        ClusterUpdateAppWorker calls -->
        Clusters::Applications::PatchService -->
      DRY req params
      Adds gcp_cluster:cluster_update_app queue
      Schedule_update_service is uneeded
      Extract common logic to a parent class (UpdateService will need it)
      Introduce new UpdateService
      Fix rescue class namespace
      Fix RuboCop offenses
      Adds BaseService for create and update services
      Remove request_handler code duplication
      Fixes update command
      Move update_command to ApplicationCore so all apps can use it
      Adds tests for Knative update_command
      Adds specs for PatchService
      Raise error if update receives an unistalled app
      Adds update_service spec
      Fix RuboCop offense
      Use subject in favor of go
      Adds update endpoint specs for project namespace
      Adds update endpoint specs for group namespace
    • Shinya Maeda's avatar
      Rename ambiguous association names in Ci::Pipeline · 18889696
      Shinya Maeda authored
      fix it ok
      head pipeline
  3. 01 Mar, 2019 4 commits
  4. 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.
  5. 26 Feb, 2019 1 commit
    • Stan Hu's avatar
      Fix Etag expiration for forked projects · c5c71299
      Stan Hu authored
      When a pipeline is for a forked merge request, we have to invalidate
      the ETag for both the target and source project pipelines. Before
      we were only invalidating the target project's pipeline.
  6. 20 Feb, 2019 1 commit
  7. 14 Feb, 2019 1 commit
    • Sarah Yasonik's avatar
      Update Metrics references to Object path · e6fcdd7a
      Sarah Yasonik authored
      On reload, references to Metrics within classes in the Gitlab::Metrics
      module fail. Update all references to ::Gitlab::Metrics so that
      constant lookup finds the right module in development. This fix should
      not impact production.
  8. 07 Feb, 2019 1 commit
  9. 06 Feb, 2019 2 commits
  10. 05 Feb, 2019 1 commit
  11. 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.
    • 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
    • Gabriel Mazetto's avatar
      Prepare rake task for storage rollback · c2c34eba
      Gabriel Mazetto authored
      We are keeping compatibility with existing scheduled jobs.
    • 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.
  12. 24 Jan, 2019 2 commits
  13. 21 Jan, 2019 2 commits
  14. 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
      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
  15. 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.
  16. 08 Jan, 2019 1 commit
  17. 07 Jan, 2019 2 commits
  18. 04 Jan, 2019 1 commit
  19. 31 Dec, 2018 1 commit
    • Jonathon Reinhart's avatar
      Add support for Git push options, specifically ci.skip · ba781484
      Jonathon Reinhart authored
      gitlab-org/gitlab-shell!166 added support for collecting push options
      from the environment, and passing them along to the
      /internal/post_receive API endpoint.
      This change handles the new push_options JSON element in the payload,
      and passes them on through to the GitPushService and GitTagPushService
      Futhermore, it adds support for the first push option, ci.skip.  With
      this change, one can use 'git push -o ci.skip' to skip CI pipe
      execution. Note that the pipeline is still created, but in the "skipped"
      state, just like with the 'ci skip' commit message text.
      Implements #18667
  20. 21 Dec, 2018 2 commits
  21. 19 Dec, 2018 1 commit
  22. 18 Dec, 2018 1 commit
  23. 12 Dec, 2018 1 commit
  24. 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.
    • Tiago Botelho's avatar
    • Douwe Maan's avatar
      Remove RemoveOldWebHookLogsWorker · 536c1e40
      Douwe Maan authored
  25. 06 Dec, 2018 1 commit
    • Jan Provaznik's avatar
      Use FastDestroy for deleting uploads · 239fdc78
      Jan Provaznik authored
      It gathers list of file paths to delete before destroying
      the parent object. Then after the parent_object is destroyed
      these paths are scheduled for deletion asynchronously.
      Carrierwave needed associated model for deleting upload file.
      To avoid this requirement, simple Fog/File layer is used directly
      for file deletion, this allows us to use just a simple list of paths.