Use ccache for Travis builds. #611
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
googlebot
added
the
cla: yes
coryan
requested review from
hemant-qlogic,
houglum,
manish-qlogic,
mbrukman,
roopak-qlogic and
sduskis
ci/build-linux.sh
Outdated
| docker_uid="${UID:-0}" | ||
| fi | ||
|
|
||
| # Use a volume to store the any cache files, so we save the cache for future |
Contributor
There was a problem hiding this comment.
'the' seems unnecessary
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change the Travis builds on Linux+CMake use ccache, speeding up many of the builds. For example, the clang-tidy build goes from ~24m to ~13m:
Before:
https://travis-ci.org/GoogleCloudPlatform/google-cloud-cpp/jobs/386452738
After (with a warm cache):
https://travis-ci.org/GoogleCloudPlatform/google-cloud-cpp/jobs/386477710
In general, branches and PRs use the cache from the master branch, so most builds should experience an improvement.
The total build time did not improve that much because it is dominated by the TEST_INSTALL=yes build:
After (with a warm cache):
https://travis-ci.org/GoogleCloudPlatform/google-cloud-cpp/jobs/386477709
I would rather address that problem in a future PR, because I would rather see the current gains deployed.