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

Proper caching #25

Closed
szepeviktor opened this issue Nov 24, 2020 · 6 comments
Closed

Proper caching #25

szepeviktor opened this issue Nov 24, 2020 · 6 comments

Comments

@szepeviktor
Copy link
Contributor

Please do not encourage users to cache vendor directory.

path: vendor/

It makes CI unpredictable.

BTW ::set-output is unused in README.

@g105b
Copy link
Member

g105b commented Nov 24, 2020

Hi @szepeviktor ,

I considered the caching of the vendor directory a useful feature (as long as the cache is validated against the composer.lock file). Please can you suggest an alternative method of doing this?

The documentation of https://github.com/actions/cache was used when forming my opinion of caching the vendor directory (the example uses the node_modules directory of an NPM project instead.

@szepeviktor
Copy link
Contributor Author

I'm not able to convince you that only the cache directory should be actually cached.
travis-ci/travis-ci#4579 (comment)

Composer can install packages from the cache to /vendor directory in 1 second!
In theory it applies also for npm, in reality npm is viktor-blacklisted, please consider using Yarn v1/v2.

@szepeviktor
Copy link
Contributor Author

Please can you suggest an alternative method of doing this?

Please see this PR #26

@g105b
Copy link
Member

g105b commented Nov 24, 2020

This is great, thanks very much. I'll check it out and merge the PR once tested.

@g105b
Copy link
Member

g105b commented Dec 3, 2020

Thanks. Merged #26.

@g105b g105b closed this as completed Dec 3, 2020
@szepeviktor
Copy link
Contributor Author

You're welcome.

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

No branches or pull requests

2 participants