Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate sonar.http.timeout (replaced by sonar.scanner.connectTimeout) #1983

Open
3 tasks
martin-strecker-sonarsource opened this issue Jun 26, 2024 · 0 comments

Comments

@martin-strecker-sonarsource
Copy link
Contributor

martin-strecker-sonarsource commented Jun 26, 2024

The newly introduced timeouts (#1977) for the scanner overlap with our sonar.http.timeout setting (#1878). It is unfortunate that there are four user-facing settings for essentially the same thing. We can not do much about the three new settings as they are defined for all scanners. But we can at least reduce the number of settings from four to three by deprecating our sonar.http.timeout setting.
Actions:

  • Add a warning about the deprecation of sonar.http.timeout with a hint about the replacement sonar.scanner.connectTimeout (see also Add support for JRE provisioning: HttpClient timeouts #1977)
  • Update the documentation
  • Turn the usage of sonar.http.timeout into an error on the next major release after the deprecation warning was introduced and remove the support for sonar.http.timeout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants