Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use composer update:lock without composer install #8

Open
rotemreiss opened this issue May 15, 2019 · 1 comment
Open

Use composer update:lock without composer install #8

rotemreiss opened this issue May 15, 2019 · 1 comment

Comments

@rotemreiss
Copy link

rotemreiss commented May 15, 2019

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 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.

@greg-1-anderson
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants