1. 16 Jun, 2019 1 commit
  2. 14 Jun, 2019 1 commit
    • Bob Van Landuyt's avatar
      Expose comments on Noteables in GraphQL · ad81ecf25a6f
      Bob Van Landuyt authored
      This exposes `Note`s on Issues & MergeRequests using a
      `Types::Notes::NoteableType` in GraphQL.
      Exposing notes on a new type can be done by implementing the
      `NoteableType` interface on the type. The presented object should
      be a `Noteable`.
  3. 13 Jun, 2019 7 commits
  4. 12 Jun, 2019 1 commit
  5. 11 Jun, 2019 1 commit
  6. 10 Jun, 2019 2 commits
  7. 07 Jun, 2019 2 commits
  8. 06 Jun, 2019 9 commits
  9. 05 Jun, 2019 7 commits
  10. 04 Jun, 2019 2 commits
  11. 03 Jun, 2019 6 commits
    • Mayra Cabrera's avatar
      Cleans up UpdateProjectStatistics concern · ca06e0c8f7bd
      Mayra Cabrera authored
      - Renames attributes from stat to project_statistiscs_name and attribute
      to statistic_attribute
      - Reordes methods on UpdateProjectStatistics concern
      - Removes unused module from Ci::Build
    • João Cunha's avatar
      Move file one folder level up to avoid namespace conflict · d038cb9c0559
      João Cunha authored
      Clusters::Cluster::KnativeServicesFinder becomes
      This is to avoid loading race condition between:
      module Clusters
        class Cluster < ApplicationRecord
      module Clusters
        class Cluster
    • Bob Van Landuyt's avatar
      Make `resolvable_types` a class method · e1a3ada4fcc1
      Bob Van Landuyt authored
      This turns Notable::RESOLVABLE_TYPES into a
      `Notable.resolvable_types`. That allows us to override it in EE.
    • Alessio Caiazza's avatar
      Add Namespace and ProjectStatistics to GraphQL API · 06b3a94ac30e
      Alessio Caiazza authored
      We can query namespaces, and nested projects.
      Projects now exposes statistics
    • Shinya Maeda's avatar
      Abstract auto merge processes · 50ce7ba2ff35
      Shinya Maeda authored
      We have one auto merge strategy today - Merge When Pipeline
      In order to add more strategies for Merge Train feature,
      we abstract the architecture to be more extensible.
      Removed arguments
      Fix spec
    • Shinya Maeda's avatar
      Make pipeline schedule worker resilient · 414b2b931514
      Shinya Maeda authored
      Currently, pipeline schedule worker is unstable because it's
      sometimes killed by excessive memory consumption.
      In order to improve the performance, we add the following fixes:
      1. next_run_at is always real_next_run, which means the value
         always takes into account of worker's cron schedule
      1. Remove exlusive lock. This is already covered by real_next_run
      1. Use RunPipelineScheduleWorker for avoiding memory killer.
         Memory consumption is spread to the multiple sidekiq worker.
  12. 31 May, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Automatically update MR merge-ref along merge status · 8ade86228d45
      Oswaldo Ferreira authored
      This couples the code that transitions the `MergeRequest#merge_status`
      and refs/merge-requests/:iid/merge ref update.
      In general, instead of directly telling `MergeToRefService` to update
      the merge ref, we should rely on `MergeabilityCheckService` to keep
      both the merge status and merge ref synced. Now, if the merge_status is
      `can_be_merged` it means the merge-ref is also updated to the latest.
      We've also updated the logic to be more systematic and less user-based.