php - Travis-CI: how to cache composer executable between builds? -

On every Travis build, the composer auto update is run. And it gets updated on every build, it is possible to do this composer executable cache as we do it through the vendor

  with the cache: the directory : - Vendor - $ HOME / .composer / cache  

I have to cache the entire /home/travis/.phpenv/versions/5.5/bin/composer But I think that this is not right because the contents of this folder can change

any suggestions (of course, custom music Excluding car)?

I advised myself not to update the composer, but handle Travis with it. (It's automatically updated every 30/60 days)

In addition, I can advise to use new container-based infrastructure to allow run and caching ...

  Language: php Sudo: Incorrect cache: Directory: - $ HOME / .composer / cache php: - 5.5 - 5.6 - 7 - hhvm Installations: - Musician Installed Script: Seller / bin / phpunit  

Pseudo: false indicates the use of statement containers cache: hear the statement If you want to cache composer binary:

- 5.5 - 5.6 - 7 - hhvm cache: Directories: - $ HOME / .composer / cache install: - travis_retry Composer auto-update & amp; Amp; Composer - Derivative - Export Pat = "$ HOME / .composer / Seller / bin: $ PATH" - Travis_traterity Composer Install - Prefer-Dest --On-Interaction Script: Seller / Bin / Fruit < P> Also, take a look as a head, if you need to test for HHVM and you need to set a date time. My method of solving it is to set it in the .i -file in my test -directory in datetime and for all test-runners in the correct folder. This is preended in installs: - Step:

  - mkdir -p /home/travis/.phpenv/versions/$(phpenv version-name) / etc / Conf.d - phpenv config-add test / phpconfig.ini  

Anyway, there is a little bit more info than your request, but I hope that this is a composer / travis / stuff Helps look for: