| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | 2020-12-17 | 1 | -2/+7 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | 2020-09-19 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | 2020-08-20 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | 2020-07-20 | 1 | -5/+5 |
| | | |||||
| * | Replace rails_helper.rb with spec_helper.rb66741-remove-spec-rails_helper-rb | Ash McKenzie | 2019-08-30 | 1 | -1/+1 |
| | | | | | | rails_helper.rb's only logic was to require spec_helper.rb. | ||||
| * | Rework retry strategy for remote mirrors | Bob Van Landuyt | 2019-08-13 | 1 | -70/+41 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | **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. | ||||
| * | Add frozen_string_literal to spec/workersfrozen_string_spec_workers | Thong Kuah | 2019-04-01 | 1 | -0/+2 |
| | | | | | Adds `# frozen_string_literal: true` to spec/workers ruby files | ||||
| * | Only send one notification for failed remote mirror | Stan Hu | 2019-01-15 | 1 | -0/+7 |
| | | | | | | | | | | | | | | Retries in Sidekiq and in the remote mirror scheduler can cause repeated attempts in quick succession if the sync fails. Each failure will then send an e-mail to all project maintainers, which can spam users unnecessarily. Modify the logic to send one notification the first time the mirror fails by setting `error_notification_sent` to `true` and reset the flag after a successful sync. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56222 | ||||
| * | Send a notification email on mirror update errors | Alejandro RodrÃguez | 2018-12-11 | 1 | -3/+10 |
| | | | | | | | The email is sent to project maintainers containing the last mirror update error. This will allow maintainers to set alarms and react accordingly. | ||||
| * | Updates from `rubocop -a` | Lin Jen-Shin | 2018-07-09 | 1 | -5/+5 |
| | | |||||
| * | Backports every CE related change from ee-5484 to CE | Tiago Botelho | 2018-05-07 | 1 | -0/+84 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |