Cache behat in .moodle-sdk

[andrewnicols]

I run a lot of feature instances when I'm working on a particular issue. I also run instances for {i,s{m,25,24}} so at any one time I have at least 6 instances and generally about double that.

When I want to run behat, on one or all of these and it's out of date, I have to update behat for each instance which takes yonks.

Can we cache the latest version of the vendor directory perhaps and rsync each module in place before a run (should be pretty fast)?

[FMCorz]

The only problem with rsyncing the vendor directory is that you still need to make sure it has the right version according to composer.json. I think it's much safer to re-do it on each install. Beside once it's done it doesn't need to be done any more. The other thing is that the vendor directory contains other things than behat stuff.

[andrewnicols]

It's okay - we can use the built-in composer functionality: http://getcomposer.org/doc/03-cli.md#composer-cache-dir

[FMCorz]

Strangely it seems to be using a cache by default.