- 22 Oct, 2019 30 commits
-
-
Matthias Käppler authored
We currently only measure the global (node-level) business in terms of jobs being processed. We would instead like to be able to know for each sidekiq process how saturated it is in terms of actual concurrency vs requested/max concurrency. This patch does the following: - add a worker/process dimension to all existing metrics - introduce a new metric to observe concurrency per process by relating "actual job count per process" to "max job count per process" we can then obtain some sort of saturation metric.
-
James Lopez authored
Block MR with OMIPS on skipped pipelines Closes #30059 See merge request gitlab-org/gitlab!18838
-
Matija Čupić authored
-
Nick Thomas authored
Add storage shards wording See merge request gitlab-org/gitlab!18732
-
Ben Bodenmiller authored
-
Bob Van Landuyt authored
API call for Resolve Vulnerability See merge request gitlab-org/gitlab!18439
-
Victor Zagorodny authored
Add resolve_vulnerability ability for User. Add POST /vulnerabilities/:id/dismiss API. Add computed state to Findings. Update the related finder and associations to support that computed state.
-
Lin Jen-Shin authored
Change url for tag push events in chat message integration See merge request gitlab-org/gitlab!18126
-
Mats Estensen authored
Instead of the branch_url being set to `/commits/<ref>` for both tags and regular pushes, branch_url is conditionally set to `/-/tags/<ref>` for tags.
-
Lin Jen-Shin authored
add dummy project data for push sample data See merge request gitlab-org/gitlab!18571
-
Thong Kuah authored
Improve pod logs API See merge request gitlab-org/gitlab!17881
-
Reuben Pereira authored
- The rollout_status is required to get pod_names, so return nil, which will cause the controller to return 202 or 204. - Return additional parameters like pods, pod_name, container_name. - pods is the names of all pods of this environment. - Return error when no pods are available. - pod_name is the name of the pod whose logs are being returned. - container_name is the name of the container within the pod whose logs are being returned. container_name can be nil when the request to k8s API was made without a container_name.
-
Jan Provaznik authored
Rename user_id to author_id for Versions See merge request gitlab-org/gitlab!18506
-
Dmitriy Zaporozhets authored
Add comment clarifying cache behavior of `GrafanaMetricsEmbedService` Closes #34526 See merge request gitlab-org/gitlab!18881
-
Sarah Yasonik authored
-
Rémy Coutable authored
Fix flaky 25_downstream_pipelines fixture See merge request gitlab-org/gitlab!18922
-
Stan Hu authored
Make documentation linter show target path See merge request gitlab-org/gitlab!18895
-
Robert Marshall authored
- We are seeing flaky documentation lint checks that do not always catch when a file inside the documentation is set with the executable bit. The check to find executable documents runs inside a subshell and its error output is not being redirected, nor would it count those errors when running `wc -l`. It seems implausible that we are failing to `cd` into the correct directory, but this is the one method I know of that would cause the `find` expression to fail silently in the logs. It is also just useful to see that yes, we are running the documentation linter against a reasonable directory in the logs. Related https://gitlab.com/gitlab-org/gitlab/issues/28010Signed-off-by: Robert Marshall <rmarshall@gitlab.com>
-
Sanad Liaquat authored
Re-raise exception if there is no response Closes #34332 See merge request gitlab-org/gitlab!18856
-
Mark Lapierre authored
It's possible that `rescue ExceptionWithResponse` could catch a type of exception that has no response. So we need to check if there is a response before we return it
-
Douglas Barbosa Alexandre authored
Allow Gitaly to work without a PG connection Closes #34205 See merge request gitlab-org/gitlab!18659
-
Zeger-Jan van de Weg authored
Gitaly didn't require a PG connection to connect to, though recently we started to pass feature flags to Gitaly in different manners. That change would now require a PG to be running. This is not ideal, especially if only for feature flags. This change rescues a bad connection error, and breaks the required dependency between PG and Gitaly. Closes https://gitlab.com/gitlab-org/gitlab/issues/34205
-
Shinya Maeda authored
-
Russell Dickenson authored
Add more information for pre and post See merge request gitlab-org/gitlab!18773
-
Evan Read authored
-
Stan Hu authored
Use long_timeout for fetch_internal_remote GRPC See merge request gitlab-org/gitlab!18908
-
Thong Kuah authored
Enable frozen string for spec/migrations See merge request gitlab-org/gitlab!18858
-
gfyoung authored
Partially addresses: https://gitlab.com/gitlab-org/gitlab/issues/27703
-
Evan Read authored
Fix confusion in background verification doc See merge request gitlab-org/gitlab!18836
-
Valery Sizov authored
-
- 21 Oct, 2019 10 commits
-
-
nnelson authored
This call is currently only used by `UpdateRepositoryStorageService`, and it can easily time out after 30 seconds for large projects. Increase it to a long timeout to ensure this doesn't fail prematurely. Encountered in https://gitlab.com/gitlab-com/gl-infra/production/issues/1250
-
Russell Dickenson authored
Fix bad image permissions See merge request gitlab-org/gitlab!18910
-
Dan Davison authored
Images shouldn't have the +x bit
-
Mayra Cabrera authored
Time limit database lock when rebasing a merge request See merge request gitlab-org/gitlab!18481
-
Mayra Cabrera authored
Expose prometheus status to monitor dashboard See merge request gitlab-org/gitlab!18289
-
Kirstie Cook authored
Add tests for presence and absence of cluster and deployment platform
-
Mayra Cabrera authored
Update Global Policy to Reject Anonymous Users For read_operations_dashboard See merge request gitlab-org/gitlab!18687
-
Jason Goodman authored
Adjust global policy
-
Stan Hu authored
Zoom meetings model and migrations See merge request gitlab-org/gitlab!17890
-
Peter Leitzen authored
Add Active Record backed class `ZoomMeeting`s to persist and validate zoom links associated to an issue. We also associate meetings to a project (via project_id) to avoid table joins. `ZoomMeeting`s can have an issue_status of `added` or `removed` which will be used to show or hide the zoom link on an issue via quick actions.
-