Next to stability the single most relevant concern we have when it comes to running our builds on Travis CI is performance. We want everyone to be able to push their changes and see the build result as quickly as possible.
So far Travis CI has lacked dedicated tools for optimizing your builds. You got
to know the wall-clock execution time of your build jobs, but it was hard to
figure out how long each command took, unless you’d prepend every single one of
your commands with
time. Other commands, such as running
git checkout [commit]
are not timed.
Starting today Travis CI measures and displays the runtime of relevant commands, such as cloning your repository, installing dependencies, running before and after scripts, and running your tests.
These per-command time tags, as we chose to call them, provide extra information for you to optimize your build. And here’s how they currently look:
Thank you, Łukasz!