Update linter config

This sets all the sub-linters to default off, allowing us to have more
fine-tuned control over which linters are being run.

This also increases the timeout for failure, which should prevent some
of the false negatives from Zuul

Change-Id: I1e0df4590ddfeba4f96459fe3ad4d5ce7ee04978
This commit is contained in:
Ian Howell 2019-10-08 08:45:17 -05:00 committed by Pete Birley
parent 30e4c9c716
commit cf8946f8ca
1 changed files with 2 additions and 4 deletions

View File

@ -1,13 +1,10 @@
# This file contains all available configuration options
# with their default values.
# options for analysis running
run:
# default concurrency is a available CPU number
concurrency: 4
# timeout for analysis, e.g. 30s, 5m, default is 1m
deadline: 1m
deadline: 3m
# exit code when at least one issue was found, default is 1
issues-exit-code: 1
@ -133,6 +130,7 @@ linters-settings:
for-loops: false # Report preallocation suggestions on for loops, false by default
linters:
disable-all: true
enable:
- dupl # Tool for code clone detection
- goconst # Finds repeated strings that could be replaced by a constant