Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-02-02 | use Gitlab::UserSettings directly as a singleton instead of ↵ | Mario de la Ossa | |
including/extending it | |||
2017-11-23 | Allow password authentication to be disabled entirely | Markus Koller | |
2017-11-01 | Fix spec. Fix usage ping. Fix warnings by adding new models and attributes. | Shinya Maeda | |
2017-10-11 | Collect usage pings `Gcp::Cluster.enabled` and `Gcp::Cluster.disabled`, ↵ | Shinya Maeda | |
instead of `Gcp::Cluster.count` | |||
2017-10-04 | Added usage ping | Kamil Trzcinski | |
2017-09-21 | Adds gitlab features and components to usage ping data. | Tiago Botelho | |
2017-09-12 | Add auto devops enabled/disabled to usage ping | Zeger-Jan van de Weg | |
2017-09-08 | Add usage ping for Auto DevOps | Zeger-Jan van de Weg | |
Fixes gitlab-org/gitlab-ce#37648 | |||
2017-08-31 | `current_application_settings` belongs on `Gitlab::CurrentSettings` | Sean McGivern | |
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form. | |||
2017-08-07 | Use correct `Environment`-class within `Gitlab` namespace | Bob Van Landuyt | |
2017-07-24 | Add Slack and JIRA services counts to Usage Data | Jarka Kadlecova | |
2017-07-19 | Add github imported projects count to usage data | Jarka Kadlecova | |
2017-06-29 | Merge branch 'zj-usage-ping-only-gl-pipelines' into 'master' | Kamil Trzciński | |
Only count GL pipelines in usage data ping Closes #33172 See merge request !12277 | |||
2017-06-27 | Split pipelines by origin on usage data | Z.J. van de Weg | |
When sending the usage data, it now includes all pipelines. This commit will split the pipelines in two; internal and external. This will lead to historical data being incorrectly marked this way. Fixes gitlab-org/gitlab-ce#33172 | |||
2017-06-27 | Add in_review_folder to usage ping | Z.J. van de Weg | |
As its hard to reliably check how many review apps there are on the clients machine, we start by checking where the type is `review`. This means the folder is called that way. This will lead to a seq scan on the table. However, this is done once a week, so the benefit of adding an index seems not to apply here. | |||
2017-05-18 | Remove Services count from usage ping payload. | Ruben Davila | |
This query was timing out and is blocking the sync of usage data for GitLab.com | |||
2017-05-11 | Add hostname to usage ping | Sean McGivern | |
2017-05-08 | Add Pipeline Schedules that supersedes experimental Trigger Schedule | Zeger-Jan van de Weg | |
2017-04-14 | Add prometheus services to usage ping | Sean McGivern | |
2017-04-14 | Add edition to usage ping | Sean McGivern | |
2017-04-14 | Add Upload count to usage data | Robert Speicher | |
2017-04-14 | Used named parameter for refreshing usage data | Stan Hu | |
2017-04-14 | Cache the last usage data to avoid unicorn timeouts | Stan Hu | |
2017-04-14 | Port 'Add uuid to usage ping' to CE | Sean McGivern | |
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1521 | |||
2017-04-14 | Track Mattermost usage | Z.J. van de Weg | |
2017-04-14 | Remove pushes count from usage ping payload | Ruben Davila | |
This query is constantly generating timeout errors on large installations and we don't have a simple solution for now and also we don't think having this counter is really critical. | |||
2017-04-14 | Port 'Add more usage data to EE ping' to CE | Sean McGivern | |
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/735 |