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

[CI] composer cache not using latest depencies #68

Open
1 of 2 tasks
jrushlow opened this issue Mar 16, 2020 · 2 comments
Open
1 of 2 tasks

[CI] composer cache not using latest depencies #68

jrushlow opened this issue Mar 16, 2020 · 2 comments
Assignees

Comments

@jrushlow
Copy link
Collaborator

jrushlow commented Mar 16, 2020

Without a lock file, composer cache in CI doesn't always use latest builds of dependencies.

  • temp. disable composer cache to use latest dev dependencies
  • solution to invalidate cache without a composer.lock file
@kbond
Copy link
Contributor

kbond commented Mar 31, 2020

I have also run into this (same with caching the phpunit directory). I never did find a solution to either and ended up just disabling the cache as well.

@stof
Copy link
Contributor

stof commented Apr 9, 2020

Well, the issue was that you were trying to skip the composer install entirely when the cache was a hit. But a hit based on composer.json is not enough for that.
You could still cache the composer cache, but without skipping the install entirely (an install from a warm cache will still help)

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

3 participants