delta/gitlab/gitlab-ce.git/config/initializers/deprecations.rb, branch docs/split-autodevops-variable-table gitlab.com: gitlab-org/gitlab-ce.git Add a rubocop for Rails.logger 2019-07-10T19:26:47+00:00 Mayra Cabrera mcabrera@gitlab.com 2019-07-10T19:26:47+00:00 0ab89d8e36ba58a95244b4c6dd49d53fac7a699f Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102 
Suggests to use a JSON structured log instead

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
Conditionally add Gitaly deprecation warnings based on ENV variable 2018-05-17T17:35:34+00:00 Stan Hu stanhu@gmail.com 2018-05-17T17:12:48+00:00 90100c26611216ac9b1c64c4ed54a8b5a20df5c9 






More verbose logging for deprecated path access
2018-05-14T13:08:51+00:00

Zeger-Jan van de Weg
git@zjvandeweg.nl

2018-05-14T13:08:51+00:00

aad2e06f4851f9236881897bf987950b772dd99a

Current logging tells us we've isolated the calls to about 5 call sites,
now we'd like to know what is calling these methods.





Current logging tells us we've isolated the calls to about 5 call sites,
now we'd like to know what is calling these methods.







Backport dev env check for storage settings deprecation
2018-04-24T20:29:44+00:00

Oswaldo Ferreira
oswaldo@gitlab.com

2018-04-18T14:24:05+00:00

132f7d33a92d69b163ed5c8a8d8dfd394da12a26












Backport GitLab domain helper methods
2018-04-13T17:52:33+00:00

Oswaldo Ferreira
oswaldo@gitlab.com

2018-04-13T17:20:29+00:00

2c8d4f1a450f15ea7e5bd731c0149287ca8e4e73












Deprecate legacy disk paths
2018-04-12T13:23:36+00:00

Zeger-Jan van de Weg
git@zjvandeweg.nl

2018-04-12T07:12:21+00:00

a752c56ca82d6f0fdee340f5d494347a4aa90072

Direct disk access is impossible on environments where components run in
their own container. There for constructing the path should not be done
except for exceptional cases.

One of the considerations, instead of logging, was to use Sentry. For
now I've chosen not to use this as the impact of this change is hard to
determine. Getting this in now will allow us to checkout the impact on
dev.gitlab.org and staging.





Direct disk access is impossible on environments where components run in
their own container. There for constructing the path should not be done
except for exceptional cases.

One of the considerations, instead of logging, was to use Sentry. For
now I've chosen not to use this as the impact of this change is hard to
determine. Getting this in now will allow us to checkout the impact on
dev.gitlab.org and staging.