From e124c4a6a26face5868167474b5e4cbdc4f2db8f Mon Sep 17 00:00:00 2001 From: Ben Patterson Date: Wed, 25 Jan 2017 07:45:34 -0500 Subject: [PATCH] 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. --- scripts/generic-ci-tests.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/generic-ci-tests.sh b/scripts/generic-ci-tests.sh index 9f97530e7d..850c24f501 100755 --- a/scripts/generic-ci-tests.sh +++ b/scripts/generic-ci-tests.sh @@ -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."