You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found this repo via thom8/faas-composer#4 and it is great for our CI!
My main goal was to improve the update performance by disabling the actual files download, and as for today it was improved by ~90% (~11 minutes to ~1 minute!!) by using composer install and composer update:lock, but I'm wondering if there's a way to run composer update:lock without first running composer install and somehow still make it recognize the new command.
Thanks.
The text was updated successfully, but these errors were encountered:
I haven't tried this, but see if composer global require g1a/composer-test-scenarios --no-dev works out. In theory, that will allow composer update:lock to be available across all projects.
I should probably separate composer update:lock into a separate plugin so that you do not need to be burdened with a global composer-test-scenarios, which may or may not cause a problem.
Hi,
Found this repo via thom8/faas-composer#4 and it is great for our CI!
My main goal was to improve the update performance by disabling the actual files download, and as for today it was improved by ~90% (~11 minutes to ~1 minute!!) by using
composer install
andcomposer update:lock
, but I'm wondering if there's a way to runcomposer update:lock
without first runningcomposer install
and somehow still make it recognize the new command.Thanks.
The text was updated successfully, but these errors were encountered: