Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.1 on 2022-01-26 at 16:00 UTC+1 (a few minutes of down time)

  1. 07 Dec, 2018 10 commits
    • Zeger-Jan van de Weg's avatar
      Allow public forks to be deduplicated · f837c22a38b1
      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.
    • Amit Rathi's avatar
    • Steve Azzopardi's avatar
      Add endpoint to download single artifact by ref · f5acf8e2b0ff
      Steve Azzopardi authored
      Add a new endpoint
      which is the close the web URL for consistency sake. This endpoint can
      be used to download a single file from artifacts for the specified ref
      and job.
    • Tiago Botelho's avatar
    • Nick Thomas's avatar
      Fix transaction pollution in Shard.by_name · 1c118b2852b2
      Nick Thomas authored
    • Nick Thomas's avatar
    • Tomasz Maczukin's avatar
      Update gitlab runner helm chart to 0.1.39 · 7d6a7f7c9144
      Tomasz Maczukin authored
    • Kamil Trzciński's avatar
      Encrypt CI/CD builds tokens · e143775103e7
      Kamil Trzciński authored
      Brings back 1e8f1de0 reverted in !23644
      Closes #52342
      See merge request gitlab-org/gitlab-ce!23436
    • Stan Hu's avatar
    • Robert Speicher's avatar
      Revert "Merge branch 'fix/gb/encrypt-ci-build-token' into 'master'" · 323bebf60ec5
      Robert Speicher authored
      This reverts commit 1e8f1de034aa9b6a60b640b2b091f60c4d3ba365, reversing
      changes made to 62d971129da99936a3cdc04f3740d26f16a0c7a6.
  2. 06 Dec, 2018 11 commits
  3. 05 Dec, 2018 7 commits
  4. 04 Dec, 2018 12 commits
    • Thong Kuah's avatar
      Eager load clusters to prevent N+1 · e568fe03f401
      Thong Kuah authored
      This also means we need to apply the `current_scope` otherwise this
      method will return all clusters associated with the groups regardless of
      any scopes applied to this method
    • Thong Kuah's avatar
      Unify into :group_clusters feature flag · 8954128c2d2d
      Thong Kuah authored
      With this MR, group clusters is now functional, so default to enabled.
      Have a single setting on the root ancestor group to enabled or disable
      group clusters feature as a whole
    • Thong Kuah's avatar
      Various improvements to hierarchy sorting · 25aaac800b56
      Thong Kuah authored
      - Rename ordered_group_clusters_for_project ->
      - Improve name of order option. It makes much more sense to have `hierarchy_order: :asc`
      and `hierarchy_order: :desc`
      - Allow ancestor_clusters_for_clusterable for group
      - Re-use code already present in Project
    • Thong Kuah's avatar
      Create k8s namespace for project in group clusters · afce416eb849
      Thong Kuah authored
      AFAIK the only relevant place is Projects::CreateService, this gets
      called when user creates a new project, forks a new project and does
      those things via the api.
      Also create k8s namespace for new group hierarchy
      when transferring project between groups
      Uses new Refresh service to create k8s namespaces
      - Ensure we use Cluster#cluster_project
      If a project has multiple clusters (EE), using Project#cluster_project
      is not guaranteed to return the cluster_project for this cluster. So
      switch to using Cluster#cluster_project - at this stage a cluster can
      only have 1 cluster_project.
      Also, remove rescue so that sidekiq can retry
    • Thong Kuah's avatar
      Teach Cluster about #all_projects · 0232c657fd39
      Thong Kuah authored
      For project level, it's the project directly associated. For group
      level, it's the projects under that group.
    • Thong Kuah's avatar
      Teach Project about #all_clusters · c3bafafd4301
      Thong Kuah authored
      This returns a union of the project level clusters and group level
      clusters associated with this project.
    • Thong Kuah's avatar
      Add association project -> kubernetes_namespaces · 821e0912c729
      Thong Kuah authored
      kubernetes_namespaces is not needed for project import/export as it
      tracks internal state of kubernetes integration
    • Thong Kuah's avatar
      Deploy to clusters for a project's groups · 25fe18a1d461
      Thong Kuah authored
      Look for matching clusters starting from the closest ancestor, then go
      up the ancestor tree.
      Then use Ruby to get clusters for each group in order. Not that
      efficient, considering we will doing up to `NUMBER_OF_ANCESTORS_ALLOWED`
      number of queries, but it's a finite number
      Explicitly order query by depth
      This allows us to control ordering explicitly and also to reverse the
      order which is useful to allow us to be consistent with
      Clusters::Cluster.on_environment (EE) which does reverse ordering.
      Puts querying group clusters behind Feature Flag. Just in case we have
      issues with performance, we can easily disable this
    • Francisco Javier López's avatar
    • Brett Walker's avatar
      Extract code into IssueBoardEntity · 5bc7013dffab
      Brett Walker authored
    • Grzegorz Bizon's avatar
    • Grzegorz Bizon's avatar