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

[feat]: caching #132

Closed
jkuri opened this Issue Sep 2, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@jkuri
Copy link
Contributor

jkuri commented Sep 2, 2017

Caching directories in builds that are not changed ofter. This will speed up builds significantly.
Good example of cached directory is node_modules/.

@jkuri jkuri added this to the 1.0 milestone Sep 2, 2017

@jkuri jkuri self-assigned this Sep 2, 2017

@jkuri jkuri closed this in 1610146 Sep 11, 2017

@captn3m0

This comment has been minimized.

Copy link

captn3m0 commented Apr 17, 2018

@jkuri Is it possible to have configurable caching? Not all languages are covered in the defaults, and I'd much rather prefer a dumb /cache mount, which is usable by just setting the cache directory path correctly. (This is how Wercker does it)

For eg: composer config cache-dir $ABSTRUSE_CACHE_DIR works better than hardcoding the path, since the vendor directory might not necessarily be in the repo root.

I like the Travis approach as well: Have some hardcoded paths for default caching support out of the box, but allow cache-mounts.

Edit: Looks like travis approach works?

@jkuri

This comment has been minimized.

Copy link
Contributor

jkuri commented Apr 17, 2018

sure, you can set cached directories like so:

cache:
  - node_modules/
  - dist/

in your .abstruse.yml configuration, here is an example.

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