GitLab steht Mittwoch, den 08. Juli, zwischen 09:00 und 13:00 Uhr aufgrund von Wartungsarbeiten nicht zur Verfügung.

  1. 19 Mar, 2019 1 commit
  2. 06 Mar, 2019 1 commit
  3. 24 Jan, 2019 1 commit
  4. 16 Jan, 2019 1 commit
    • Alejandro Rodríguez's avatar
      Return max group access level in the projects API · ab94a5a5
      Alejandro Rodríguez authored
      Currently if a project is inside a nested group and a user doesn't have
      specific permissions for that group but does have permissions on a
      parent group the `GET /projects/:id` API call will return the following
      permissions:
      
      ```json
      permissions: { project_access: null, group_access: null }
      ```
      
      It could also happen that the group specific permissions are of lower
      level than the ones the user has in parent groups. This patch makes it
      so that the permission returned for `group_access` is the highest from
      amongst the hierarchy, which is (ostensibly) the information that the
      API user is interested in for that field.
      ab94a5a5
  5. 19 Dec, 2018 1 commit
  6. 04 Dec, 2018 1 commit
    • Thong Kuah's avatar
      Unify into :group_clusters feature flag · ebf87fd9
      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
      ebf87fd9
  7. 03 Dec, 2018 1 commit
  8. 16 Nov, 2018 1 commit
  9. 30 Oct, 2018 1 commit
  10. 29 Oct, 2018 1 commit
    • Thong Kuah's avatar
      Associate clusters model to groups · 0e15eec8
      Thong Kuah authored
      Even though we currently only should have one group for a cluster, we
      allow the flexibility to associate to other groups in the future.
      
      This also matches the runner <=> groups association.
      
      - Adds Cluster#first_group, aliased to Cluster#group. For the
      conceivable future, a cluster will have at most one group.
      
      - Prevent mixing of group and project clusters. If project type
      clusters, it should only have projects assigned.  Similarly with groups.
      
      - Default cluster_type to :project_type. As it's very small table we can
      set default and null: false in one release.
      0e15eec8
  11. 24 Sep, 2018 1 commit
  12. 17 Sep, 2018 1 commit
    • Yorick Peterse's avatar
      Added FromUnion to easily select from a UNION · 8a72f5c4
      Yorick Peterse authored
      This commit adds the module `FromUnion`, which provides the class method
      `from_union`. This simplifies the process of selecting data from the
      result of a UNION, and reduces the likelihood of making mistakes. As a
      result, instead of this:
      
          union = Gitlab::SQL::Union.new([foo, bar])
      
          Foo.from("(#{union.to_sql}) #{Foo.table_name}")
      
      We can now write this instead:
      
          Foo.from_union([foo, bar])
      
      This commit also includes some changes to make this new setup work
      properly. For example, a bug in Rails 4
      (https://github.com/rails/rails/issues/24193) would break the use of
      `from("sub-query-here").includes(:relation)` in certain cases. There was
      also a CI query which appeared to repeat a lot of conditions from an
      outer query on an inner query, which isn't necessary.
      
      Finally, we include a RuboCop cop to ensure developers use this new
      module, instead of using Gitlab::SQL::Union directly.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/51307
      8a72f5c4
  13. 11 Sep, 2018 1 commit
  14. 06 Aug, 2018 1 commit
  15. 02 Aug, 2018 1 commit
  16. 27 Jul, 2018 1 commit
  17. 11 Jul, 2018 2 commits
  18. 03 Jul, 2018 2 commits
  19. 07 Jun, 2018 1 commit
  20. 06 Jun, 2018 1 commit
  21. 16 May, 2018 2 commits
    • Jan Provaznik's avatar
      Changed order of include · 32e22468
      Jan Provaznik authored
      32e22468
    • Jan Provaznik's avatar
      Delete remote uploads · 7da3b2cd
      Jan Provaznik authored
      ObjectStore uploader requires presence of associated `uploads` record
      when deleting the upload file (through the carrierwave's after_commit
      hook) because we keep info whether file is LOCAL or REMOTE in `upload`
      object.
      
      For this reason we can not destroy uploads as "dependent: :destroy" hook
      because these would be deleted too soon. Instead we rely on
      carrierwave's hook to destroy `uploads` in after_commit hook.
      
      But in before_destroy hook we still have to delete not-mounted uploads
      (which don't use carrierwave's destroy hook). This has to be done in
      before_Destroy instead of after_commit because `FileUpload` requires
      existence of model's object on destroy action.
      
      This is not ideal state of things, in a next step we should investigate
      how to unify model dependencies so we can use same workflow for all
      uploads.
      
      Related to #45425
      7da3b2cd
  22. 04 May, 2018 1 commit
  23. 02 May, 2018 1 commit
  24. 23 Apr, 2018 4 commits
  25. 18 Apr, 2018 1 commit
    • Yorick Peterse's avatar
      Revert the addition of goldiloader · 6f292eaa
      Yorick Peterse authored
      This reverts the addition of the "goldiloader" Gem and all use of it.
      While this Gem is very promising it's causing a variety of problems on
      GitLab.com due to it eager-loading too much data in places where we
      don't expect/can handle this. At least for the time being this means we
      have to go back to manually fixing N+1 query problems, but at least
      those should not cause a negative impact on availability.
      6f292eaa
  26. 09 Apr, 2018 1 commit
  27. 06 Apr, 2018 1 commit
  28. 04 Apr, 2018 1 commit
  29. 22 Mar, 2018 1 commit
  30. 21 Mar, 2018 1 commit
  31. 05 Mar, 2018 1 commit
  32. 03 Mar, 2018 1 commit
  33. 28 Feb, 2018 2 commits