I've been working on Commerce Kickstart lately and trying to boost build speed. One thing that I've tested is caching $HOME/.composer/cache and $HOME/.drush/cache.
Due to concurrency the first few don't have a cache, but after first build completes all others can share cache.
Here's a build I'll reference: https://travis-ci.org/mglaman/commerce_kickstart/builds/72297631
Build 124.2:
Build 124.9 (cached)
Those numbers average pretty well across cached/non-cached builds Overall it's about a minute saved, which at 21 builds is a good chunk of time!
Patch inc
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | cache_drush_and-2538634-4.patch | 1.35 KB | dsnopek |
Comments
Comment #1
mglamanPatch!
Comment #2
dsnopekThanks! That's actually less than I would have thought would have been saved. Although, the times on Commerce Kickstart are much lower than Panopoly in general, so maybe we'll save much more. :-) For testing purposes, can you make a patch that sets 'sudo: false' and comments out the Chrome tests? Then we can try running it and see exactly how good it does!
Comment #3
mglamanLike this?
Comment #4
dsnopekThanks! Here's the Travis build:
https://travis-ci.org/dsnopek/panopoly
I modified the patch a little bit so we weren't specifying 'sudo' twice. That patch is attached.
Comment #5
dsnopekThere were lots of failures (which I think will get fixed in #2532134: Migrate to new Travis infrastructure eventually) but it's definitely very fast! Watching some of the later builds, it breezes through the drush make and composer bits. Unfortunately, we don't have any timing in our script to see exact numbers.
Comment #6
dsnopekNow that #2532134: Migrate to new Travis infrastructure has landed, I've re-rolled and merged this as well! Thanks, @mglaman!