Closed ltiao closed 8 years ago
Is the log being stored in a file or being sent to stdout? If it's stdout we can just redirect it into oblivion.
The stdout is just written to a log, which Travis CI stores. We don't necessarily want to redirect everything to dev/null
though, since some messages are informative. The ones that are not, for example, are those that list the content of tarfiles as its being extracted (i.e. the verbose option v
in tar -xvf
).
Another problem that might bite us in the future is the build time. Currently every build will require downloading/building boost from scratch which takes ages. Do you think having the option to use the system boost libraries would be a good idea to speed up build times?
This sets up Travis CI to build the Docker image from the Dockerfile. Currently, Travis CI will report failure as the log from the Docker build exceeds 4MB and immediately aborts. Will need to find a way to suppress some output and decrease verbosity when invoked by Travis CI.