1. 01 Apr, 2019 3 commits
  2. 29 Mar, 2019 2 commits
  3. 28 Mar, 2019 1 commit
  4. 27 Mar, 2019 3 commits
    • Vladimir Shushlin's avatar
      Refactor verify_pages_domain_service specs · c29f4416
      Vladimir Shushlin authored
      Add specs for new/disabled pages domain
      Extract contexts from examples
      Use `let` instead of `set` since domain is being changed
      in each example
      c29f4416
    • Nick Thomas's avatar
      Allow external diffs to be used conditionally · 0e831b0b
      Nick Thomas authored
      Since external diffs are likely to be a bit slower than in-database
      ones, add a mode that makes diffs external after they've been obsoleted
      by events. This should strike a balance between performance and disk
      space.
      
      A background cron drives the majority of migrations, since diffs become
      outdated through user actions.
      0e831b0b
    • Oswaldo Ferreira's avatar
      Prepare suggestion implementation for multi-line · 03e0604d
      Oswaldo Ferreira authored
      Adds the groundwork needed in order to persist multi-line suggestions,
      while providing the parsing strategy which will be reused for the
      **Preview** as well.
      03e0604d
  5. 26 Mar, 2019 4 commits
  6. 25 Mar, 2019 3 commits
  7. 22 Mar, 2019 1 commit
  8. 20 Mar, 2019 2 commits
    • Tiger's avatar
      Add feature flag for build preparing state · 759dab5b
      Tiger authored
      The flag is on by default, but allows us to revert back
      to the old behaviour if we encounter any problems.
      759dab5b
    • Tiger's avatar
      Create framework for build prerequisites · 00f0d356
      Tiger authored
      Introduces the concept of Prerequisites for a CI build.
      If a build has unmet prerequisites it will go through the
      :preparing state before being made available to a runner.
      
      There are no actual prerequisites yet, so current
      behaviour is unchanged.
      00f0d356
  9. 18 Mar, 2019 1 commit
  10. 13 Mar, 2019 1 commit
  11. 12 Mar, 2019 1 commit
  12. 08 Mar, 2019 1 commit
  13. 07 Mar, 2019 1 commit
  14. 06 Mar, 2019 3 commits
  15. 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
      3bdff7aa
    • 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 -->
        ClusterWaitForAppInstallationWorker
      
      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
      f8234d9a
    • Gabriel Mazetto's avatar
      Skip project validation when switching storage layouts · b4f20502
      Gabriel Mazetto authored
      This is a fix for the Hashed Storage migration and Rollback procedure
      to ignore any project-level validation error that can happen in a
      long-running instance.
      
      There are many situations where defaults and acceptable values changed
      but, because we didn't provide a migration to "valid" attributes, it
      can happen that project will not be `valid? => true`.
      
      Because the changes we are making are limited to setting a project as
      read_only or changing the storage_level, it's safe to bypass validation.
      b4f20502
  16. 04 Mar, 2019 1 commit
  17. 02 Mar, 2019 1 commit
  18. 01 Mar, 2019 8 commits