ba01621de5
The performance improvement offered by the build cache is modest when run by Travis CI. This is probably because Travis CI does not keep the cache on any local machine. Instead, Travis CI uploads the build cache across a network at the end of each run, then restores the cache across the network at the start of the next run. So in many cases we're simply trading network access to original downloads for network access to the cache image. Furthermore, it's probably a better test to perform Travis CI testing jobs from something closer to a clean slate. We really want to know whether everything builds and passes tests correctly starting from nothing. We don't want to risk accidentally thinking something would work simply because we have a cached copy of what it did when it worked previously. |
||
|---|---|---|
| .. | ||
| before-cache-gradle | ||
| before-cache-maven | ||
| before-install-gradle | ||
| before-install-maven | ||
| install-gradle | ||
| install-maven | ||
| script-gradle | ||
| script-maven | ||