- 16 Dec, 2019 40 commits
-
-
Michael Kozono authored
This reverts merge request !20294
-
Walmyr Lima e Silva Filho authored
Simplify the "issues weight" end-to-end test See merge request gitlab-org/gitlab!21754
-
Evan Read authored
Update cohorts docs with new image See merge request gitlab-org/gitlab!21632
-
Nick Thomas authored
Capture author and created_at data for Version See merge request gitlab-org/gitlab!17322
-
Mike Greiling authored
Move escapeFileUrl to shared url_utility See merge request gitlab-org/gitlab!21865
-
Walmyr Lima e Silva Filho authored
Prefer let instead of instance variable on test See merge request gitlab-org/gitlab!21758
-
Michael Kozono authored
Upgrade Gitaly to v1.76.0 See merge request gitlab-org/gitlab!21857
-
GitalyBot authored
-
Grzegorz Bizon authored
Add protected branch permission check to run downstream pipelines See merge request gitlab-org/gitlab!20964
-
Mike Greiling authored
Enable no-jquery/slim ESLint profile See merge request gitlab-org/gitlab!21775
-
Winnie Hellmann authored
-
Luke Duncalfe authored
And adding a missing spec for the event data.
-
Luke Duncalfe authored
https://gitlab.com/gitlab-org/gitlab/merge_requests/17316 introduced new user_id and created_at columns for `Versions` https://gitlab.com/gitlab-org/gitlab/merge_requests/18506 renamed this column to author_id. This MR has the app capture a `author_id` when new versions are created. It also contains a post-migration to backfill author and created_at data for `Version`s by sourcing from `Commit`s. https://gitlab.com/gitlab-org/gitlab/issues/32081 https://gitlab.com/gitlab-org/gitlab/issues/13426
-
Paul Slaughter authored
**Why?** This is no longer needed in just the IDE. We also need it to make sure we properly escape paths in the file finder.
-
Douglas Barbosa Alexandre authored
Make use of uncached diffs where highlighting is not required Closes #43654 See merge request gitlab-org/gitlab!21842
-
Mayra Cabrera authored
Add indexes on deployments to improve environments search Closes #55353 See merge request gitlab-org/gitlab!21789
-
Robert Speicher authored
Previously it sounded like we'd always target the fork, regardless of where the MR was opened.
-
Clement Ho authored
Replace var with const / let in notes.js Closes #36269 See merge request gitlab-org/gitlab!21845
-
Winnie Hellmann authored
(cherry picked from commit 0e4b14cd3b10f78a6a0686424a0ee0dc7b94c7a0)
-
Douglas Barbosa Alexandre authored
Reuse prometheus chart values when editing alerts See merge request gitlab-org/gitlab!21344
-
Walmyr Lima authored
This commit applies only to the project variable. I couldn't find a way to not use the instance variable for the issue.
-
Walmyr Lima authored
By leaving the project fabrication to the milestone fabrication since it creates it by default if none is provided.
-
Martin Wortschack authored
Fix init_create_cluster_spec timing out See merge request gitlab-org/gitlab!21856
-
Kamil Trzciński authored
Limit max metrics embeds to 100 See merge request gitlab-org/gitlab!21356
-
Sarah Yasonik authored
Limits the maximum number of metrics embeds in a single GFM field to 100 to help with loading. OVer 100 has a hard time loading.
-
Dan Davison authored
Feature spec for cluster health board See merge request gitlab-org/gitlab!20839
-
Olena Horal-Koretska authored
For some reason we need to create clusters_applications_prometheus before stubbing Kube client discover request
-
Stan Hu authored
To load diffs and other files, we make two SELECT calls in `MergeRequest#environments_for`: one for the source branch, and one for the target branch. The source branch query makes a subquery: ```sql SELECT environment_id FROM deployments WHERE project_id = 123 AND ref = 'source_branch' ``` The target branch makes this subquery: ```sql SELECT environment_id FROM deployments WHERE project_id = 123 AND (ref = 'master' OR tag IS TRUE) ``` Both subqueries were taking over 250 ms to execute. When we add an index for the deployments table on `(projects_id, ref)`, this execution drops down to under 5 ms since the table usually has a small number of rows for the source branch. Adding a partial index on `projects_id WHERE tag IS TRUE` allows PostgreSQL to perform two separate indexed scans: one for the ref, and one for the tag condition. However, this query still takes 60 ms to run for the gitlab-org/gitlab project because `master` has 10,000+ rows. We should consider adding a LIMIT in a future iteration. Closes https://gitlab.com/gitlab-org/gitlab/issues/55353
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
Imre Farkas authored
Generate sample Prometheus data See merge request gitlab-org/gitlab!19987
-
Kirstie Cook authored
Interpolate metric queries Use yml for sample metric output to easily convert hash Create a file for each metric Replace metrics endpoint if using sample data Need to create sample_metrics directory to run test Moveing logic out of the controller Insert live endpoint Add specs for SampleMetricsService Cleaning up controller specs Return 404 instead of 500 when file is not found
-
Paul Slaughter authored
**How?** There's a dynamic loading in the test subject. This causes the first spec to timeout past the 500ms threshold. By eagerly loading this module in the spec file, the module load time is no longer accounted for in the spec time.
-
Natalia Tepluhina authored
Implement bulk of Threat Monitoring store and filters component See merge request gitlab-org/gitlab!21689
-
Mark Florian authored
Part of [WAF statistics reporting][1]. This adds the bulk of the Vuex store for fetching environments and the WAF statistics, and the filter bar component which allows selection of the current environment. This also: - Aligns the UI with the latest designs, including the help link popover, copy, and the alert variant - Fixes/improves existing tests (avoiding verbose snapshots) [1]: https://gitlab.com/gitlab-org/gitlab/issues/14707
-
Hordur Freyr Yngvason authored
Alerts for the GitLab-managed app Prometheus are updated via helm. Prior to this change, when alerts were updated, all helm values would receive the current contents of `values.yaml`, with the `alerts` section overridden, or falling back to the default chart values. This meant that any time we made changes to `values.yaml` affecting component versions (e.g. the versions of prometheus or alertmanager), those would trigger a deployment of those component in the cluster, potentially breaking the prometheus installation. This was a very real problem, since we currently have hardcoded versions of both prometheus server and alertmanager in `values.yaml`, and would like to update the chart and remove the hardcoded versions in a single change. With this change, alert updates no longer take any values from `values.yaml`; instead they only update alerts. We avoid reverting to default chart values by using helm's `--reuse-values` flag instead of the `--reset-values` flag. See https://gitlab.com/gitlab-org/gitlab/issues/38294
-
Grzegorz Bizon authored
Update Serverless docs for using an older version of gitlabktl Closes #35655 See merge request gitlab-org/gitlab!21688
-
Natalia Tepluhina authored
Fix padding structure on design comments See merge request gitlab-org/gitlab!21839
-
Mayra Cabrera authored
Sync security branches using the Merge Train Closes #38387 See merge request gitlab-org/gitlab!21647
-
Kamil Trzciński authored
Fix logs menu active state (cont) See merge request gitlab-org/gitlab!21828
-