- 14 Aug, 2019 15 commits
-
-
Kushal Pandya authored
Added a downward chevron sprite icon to environments dropdown in Ultimate Closes #11562 See merge request gitlab-org/gitlab-ee!14711
-
GitLab Bot authored
-
Tim Zallmann authored
Adjust copy for adding additional members See merge request gitlab-org/gitlab-ce!31726
-
Tim Zallmann authored
Change invite text See merge request gitlab-org/gitlab-ee!15130
-
Grzegorz Bizon authored
Refactor away STATUS_MAP See merge request gitlab-org/gitlab-ee!14054
-
GitLab Bot authored
-
Achilleas Pipinellis authored
Fix spelling of "timeouted" to "timed out" See merge request gitlab-org/gitlab-ce!31774
-
GitLab Bot authored
-
Achilleas Pipinellis authored
Documentation: fix push options capabilities See merge request gitlab-org/gitlab-ce!31792
-
Christian Couder authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31068 forgot to add a short description of the new push options that it added.
-
Thong Kuah authored
It's only used internally and is really a copy of the constants in Gitlab::Kubernetes::Pod
-
GitLab Bot authored
-
Achilleas Pipinellis authored
Embed metrics charts in issues - docs See merge request gitlab-org/gitlab-ce!30849
-
Tristan Read authored
-
Achilleas Pipinellis authored
Docs: remove extra quote from doc/install/installation.md See merge request gitlab-org/gitlab-ce!31785
-
- 13 Aug, 2019 25 commits
-
-
Douwe Maan authored
Change vulnerability name to message See merge request gitlab-org/gitlab-ee!15125
-
Tetiana Chupryna authored
-
GitLab Bot authored
-
Michael Kozono authored
CE Migration Backport: Add flag to object storage See merge request gitlab-org/gitlab-ce!31695
-
Michael Kozono authored
Make Object Storage synchronization in Geo Nodes configurable via Admin UI See merge request gitlab-org/gitlab-ee!15139
-
GitLab Bot authored
-
Robert Speicher authored
Fix project avatar image in Slack pipeline notifications Closes #66008 See merge request gitlab-org/gitlab-ce!31788
-
GitLab Bot authored
-
Stan Hu authored
Add usage pings for source code pushes See merge request gitlab-org/gitlab-ce!31734
-
Igor authored
Source Code Usage Ping for Create SMAU
-
GitLab Bot authored
-
Douglas Barbosa Alexandre authored
Bump Helm to 2.14.3 and kubectl to 1.11.10 See merge request gitlab-org/gitlab-ce!31716
-
GitLab Bot authored
-
Stan Hu authored
Expand variables only when needed See merge request gitlab-org/gitlab-ce!31772
-
GitLab Bot authored
-
Douwe Maan authored
Rework push mirror retries See merge request gitlab-org/gitlab-ce!31247
-
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.
-
Douwe Maan authored
[EE] Rework push mirror retries See merge request gitlab-org/gitlab-ee!14974
-
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.
-
GitLab Bot authored
-
Douwe Maan authored
Only expire tag cache once per push See merge request gitlab-org/gitlab-ce!31641
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-