1. 30 Apr, 2019 1 commit
    • Shinya Maeda's avatar
      Fix environment automatic on_stop trigger · daa8f784
      Shinya Maeda authored
      Due to the nature of pipelines for merge requests, deployments.ref can
      be a merge request ref instead of a branch name.
      
      We support the environment auto-stop hook for this case
      daa8f784
  2. 17 Jul, 2018 1 commit
  3. 25 Apr, 2018 1 commit
    • Sean McGivern's avatar
      Move NotificationService calls to Sidekiq · b5042e53
      Sean McGivern authored
      The NotificationService has to do quite a lot of work to calculate the
      recipients for an email. Where possible, we should try to avoid doing this in an
      HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to
      schedule those emails immediately.
      
      This commit creates a generic Sidekiq worker that uses Global ID to serialise
      and deserialise its arguments, then forwards them to the NotificationService.
      The NotificationService gains an `#async` method, so you can replace:
      
          notification_service.new_issue(issue, current_user)
      
      With:
      
          notification_service.async.new_issue(issue, current_user)
      
      And have everything else work as normal, except that calculating the recipients
      will be done by Sidekiq, which will then schedule further Sidekiq jobs to send
      each email.
      b5042e53
  4. 02 Jan, 2018 1 commit
  5. 19 Sep, 2017 1 commit
    • Yorick Peterse's avatar
      Fix refreshing of issues/MR count caches · 57b96eb6
      Yorick Peterse authored
      This ensures the open issues/MR count caches are refreshed properly when
      creating new issues or MRs. This MR also includes a change to the cache
      keys to ensure all caches are rebuilt on the fly.
      
      This particular problem was not caught in the test suite due to a null
      cache being used, resulting in all calls that would use a cache using
      the underlying data directly. In production the code would fail because
      a newly saved record returns an empty hash in #changes meaning checks
      such as `state_changed? || confidential_changed?` would return false for
      new rows, thus never updating the counters.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/38061
      57b96eb6
  6. 19 Jul, 2017 1 commit
    • Sean McGivern's avatar
      Clear issuable counter caches on update · 0e488ef7
      Sean McGivern authored
      When an issuable's state changes, or one is created, we should clear the cache
      counts for a user's assigned issuables, and also the project-wide caches for
      this user type.
      0e488ef7
  7. 26 May, 2017 1 commit
  8. 12 Aug, 2016 1 commit
  9. 20 Feb, 2016 2 commits
  10. 26 Jan, 2015 1 commit
  11. 20 Jan, 2015 1 commit
  12. 02 Apr, 2014 1 commit