wget progress in travis makes the web log hard to read

[jkremser]

meanwhile in the travis log:

...
+ wget https://archive.apache.org/dist/spark/spark-2.4.0/spark-2.4.0-bin-hadoop2.7.tgz -O /tmp/artifacts/spark-2.4.0-bin-hadoop2.7.tgz
--2019-05-30 13:51:04--  https://archive.apache.org/dist/spark/spark-2.4.0/spark-2.4.0-bin-hadoop2.7.tgz
Resolving archive.apache.org (archive.apache.org)... 163.172.17.199
Connecting to archive.apache.org (archive.apache.org)|163.172.17.199|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 227893062 (217M) [application/x-gzip]
Saving to: '/tmp/artifacts/spark-2.4.0-bin-hadoop2.7.tgz'
   0K .......... .......... .......... .......... ..........  0%  233K 15m55s
    50K .......... .......... .......... .......... ..........  0%  457K 12m1s
   100K .......... .......... .......... .......... ..........  0% 33.0M 8m3s

-- https://travis-ci.org/radanalyticsio/openshift-spark/jobs/539227949#L1333

then ~4.5k lines follows. So to sum it up, from 10k lines that are allocated for the web view we use almost half for the wget progressbar :D

it's still possible to get the raw log file in plain text, but why if there is:

λ wget --help | grep quiet
  -q,  --quiet                     quiet (no output)
  -nv, --no-verbose                turn off verboseness, without being quiet

note: -nv is better because it won't be completely silent, however the "TUI-progress" bar wont be there.

[elmiko]

totally agree, i think -nv is a sensible option for these downloads.