An error occurred fetching the project authors.
  1. 14 Aug, 2019 3 commits
  2. 13 Aug, 2019 2 commits
    • Bob Van Landuyt's avatar
      Rework retry strategy for remote mirrors · 452bc36d
      Bob Van Landuyt authored
      **Prevention of running 2 simultaneous updates**
      
      Instead of using `RemoteMirror#update_status` and raise an error if
      it's already running to prevent the same mirror being updated at the
      same time we now use `Gitlab::ExclusiveLease` for that.
      
      When we fail to obtain a lease in 3 tries, 30 seconds apart, we bail
      and reschedule. We'll reschedule faster for the protected branches.
      
      If the mirror already ran since it was scheduled, the job will be
      skipped.
      
      **Error handling: Remote side**
      
      When an update fails because of a `Gitlab::Git::CommandError`, we
      won't track this error in sentry, this could be on the remote side:
      for example when branches have diverged.
      
      In this case, we'll try 3 times scheduled 1 or 5 minutes apart.
      
      In between, the mirror is marked as "to_retry", the error would be
      visible to the user when they visit the settings page.
      
      After 3 tries we'll mark the mirror as failed and notify the user.
      
      We won't track this error in sentry, as it's not likely we can help
      it.
      
      The next event that would trigger a new refresh.
      
      **Error handling: our side**
      
      If an unexpected error occurs, we mark the mirror as failed, but we'd
      still retry the job based on the regular sidekiq retries with
      backoff. Same as we used to
      
      The error would be reported in sentry, since its likely we need to do
      something about it.
      452bc36d
    • Heinrich Lee Yu's avatar
      Improve quick action error messages · 7a6ecbcb
      Heinrich Lee Yu authored
      Standardize punctuation and format
      7a6ecbcb
  3. 12 Aug, 2019 5 commits
  4. 10 Aug, 2019 1 commit
  5. 09 Aug, 2019 5 commits
  6. 08 Aug, 2019 3 commits
  7. 07 Aug, 2019 7 commits
  8. 06 Aug, 2019 2 commits
  9. 04 Aug, 2019 1 commit
    • Tiger's avatar
      Allow Cert-Manager to be uninstalled · cfe8024e
      Tiger authored
      Our current version of Cert-Manager does not uninstall
      cleanly, and we must manually remove custom resource
      definitions.
      cfe8024e
  10. 02 Aug, 2019 4 commits
  11. 01 Aug, 2019 1 commit
  12. 31 Jul, 2019 4 commits
    • Nick Thomas's avatar
      Run rake gettext:regenerate · e38c683e
      Nick Thomas authored
      e38c683e
    • Reuben Pereira's avatar
      Add prometheus listen address to whitelist · f5213a38
      Reuben Pereira authored
      - Add to whitelist so that even if local requests from hooks and
      services are not allowed, the prometheus manual configuration will
      still succeed.
      f5213a38
    • João Cunha's avatar
      Allow knative do be uninstalled: · d7c7ebf5
      João Cunha authored
      - After uninstalling the knative helm chart it's necessary to also
      remove some leftover resources to allow the cluster to be clean
      and knative to be reinstalleable.
      - Adds knative uninstall disclaimer
      - Uninstall ksvc before uninstalling knative
      
      Make list of Knative and Ingres resources explicit
      
      - To avoid deleting unwanted resources we are listing exact
      which resources will be deleted rather than simply deleting any
      resource that contains istio or knative words.
      d7c7ebf5
    • Reuben Pereira's avatar
      Allow blank but not nil in validations · 5c7f2853
      Reuben Pereira authored
      - The most common use case for qualified_domain_validator currently is
      to allow blank ([]) but not allow nil. Modify the
      qualified_domain_validator to support this use case.
      5c7f2853
  13. 30 Jul, 2019 2 commits
    • Diego Louzán's avatar
      Add support page link in help menu · e2053808
      Diego Louzán authored
      Creates a new item in help dropdown to show configured support page link
      e2053808
    • Sean McGivern's avatar
      Remove line profiler from performance bar · 18cdc5ba
      Sean McGivern authored
      1. The output isn't great. It can be hard to find hotspots and, even
         when you do find them, to find why those are hotspots.
      2. It uses some jQuery-specific frontend code which we can remove now
         that we don't have this any more.
      3. It's only possible to profile the initial request, not any subsequent
         AJAX requests.
      18cdc5ba