1. 08 Feb, 2019 2 commits
  2. 06 Feb, 2019 1 commit
  3. 04 Feb, 2019 1 commit
  4. 01 Feb, 2019 1 commit
  5. 31 Jan, 2019 1 commit
  6. 29 Jan, 2019 1 commit
  7. 25 Jan, 2019 2 commits
  8. 24 Jan, 2019 1 commit
  9. 22 Jan, 2019 1 commit
  10. 15 Jan, 2019 1 commit
  11. 09 Jan, 2019 1 commit
  12. 07 Jan, 2019 1 commit
  13. 04 Jan, 2019 5 commits
  14. 31 Dec, 2018 2 commits
    • Shinya Maeda's avatar
      Add spec for Release API · 8f1e96c8
      Shinya Maeda authored
      Add spec for all release API - GET, POST, PUT, DELETE.
      Also, fixes some minior bugs.
      8f1e96c8
    • Alessio Caiazza's avatar
      Add releases API · 1ea2d9fa
      Alessio Caiazza authored
      This commit introduces Releases API under /api/v4/projects/:id/releases
      
      * We are introducing release policies at project level.
      * We are deprecating releases changes from tags, both api and web
      interface.
      * Tags::CreateService no longer create a release
      
      This feature is controlled by :releases_page feature flag
      1ea2d9fa
  15. 25 Dec, 2018 1 commit
  16. 20 Dec, 2018 1 commit
  17. 19 Dec, 2018 2 commits
  18. 13 Dec, 2018 2 commits
  19. 12 Dec, 2018 1 commit
  20. 07 Dec, 2018 1 commit
    • 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
  21. 04 Dec, 2018 2 commits
    • Thong Kuah's avatar
      Modify service so that it can be re-run · dc182720
      Thong Kuah authored
      If the service fails mid-point, then we should be able to re-run this
      service. So, detect presence of any previously created Kubernetes
      resource and update or create accordingly.
      
      Fix specs accordingly. In the case of finalize_creation_service_spec.rb,
      I decided to stub out the async worker rather than maintaining
      individual stubs for various kubeclient calls for that worker.
      
      Also add test cases for group clusters
      dc182720
    • Thong Kuah's avatar
      Fallback to admin token for project clusters only · a97d8767
      Thong Kuah authored
      We do not want group level clusters to fall back to what was old
      behaviour for project level clusters. So instead we will not return any
      KUBE_TOKEN if we cannot find a suitable kubernetes_namespace for the
      project, in the group level cluster case.
      
      Add test cases to assert above
      a97d8767
  22. 29 Nov, 2018 1 commit
  23. 27 Nov, 2018 2 commits
    • Tiago Botelho's avatar
      Removes all the irrelevant import related code and columns · 4bd8a427
      Tiago Botelho authored
      Clears the import related columns and code from the Project
      model over to the ProjectImportState model
      4bd8a427
    • Zeger-Jan van de Weg's avatar
      Rename the Repository table to PoolRepository · fff77541
      Zeger-Jan van de Weg authored
      To separate the different kinds of repositories we have at GitLab this
      table will be renamed to pool_repositories. A project can, for now at
      least, be member of none, or one of these. The table will get additional
      columns in a later merge request where more logic is implemented for the
      model.
      
      Further included is a small refactor of logic around hashing ids for the
      disk_path, mainly to ensure a previous implementation is reusable.
      
      The disk_path for the pool_repositories table no longer has a NOT NULL
      constraint, but given the hashing of the ID requires the DB to assign
      the record an ID, an after_create hook is used to update the value.
      
      A related MR is:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23143, adding
      tables for 'normal' repositories and wiki_repositories.
      fff77541
  24. 26 Nov, 2018 2 commits
  25. 21 Nov, 2018 1 commit
    • Alessio Caiazza's avatar
      Validate URI scheme also for internal URI · 759c5296
      Alessio Caiazza authored
      Gitlab::UrlBlocker ignores scheme when validating URI matching either
      config.gitlab or config.gitlab_shell
      
      This patch enforces matching config.gitlab.protocol for internal web and
      ssh for internal shell.
      759c5296
  26. 20 Nov, 2018 3 commits