Print the paver output for python cyclomatic complexity to console.
The actual report will continue to be piped into reports/python_complexity.log. By exposing the paver output (approx 4 lines), we'll be able to consume the actual complexity number in our logs and therefore trend the results in our log aggregator.
This commit is contained in:
@@ -83,7 +83,7 @@ case "$TEST_SUITE" in
|
||||
echo "Finding ESLint violations and storing report..."
|
||||
paver run_eslint -l $ESLINT_THRESHOLD > eslint.log || { cat eslint.log; EXIT=1; }
|
||||
echo "Running code complexity report (python)."
|
||||
paver run_complexity > reports/code_complexity.log || echo "Unable to calculate code complexity. Ignoring error."
|
||||
paver run_complexity || echo "Unable to calculate code complexity. Ignoring error."
|
||||
echo "Running safe template linter report."
|
||||
paver run_safelint -t $SAFELINT_THRESHOLDS > safelint.log || { cat safelint.log; EXIT=1; }
|
||||
echo "Running safe commit linter report."
|
||||
|
||||
Reference in New Issue
Block a user