<commit_before>---
title: Dependency Cache on Codeship Basic
weight: 85
tags:
  - cache
  - dependencies
category: Getting Started
---

<div class="info-block">
Note that this article addresses caching on **Codeship Basic**. If you are looking for information on caching with **Codeship Pro**, [click here]({{ site.baseurl }}{% link _pro/getting-started/caching.md %})
</div>

## Automatic Dependency Caching

On all Codeship Basic projects, we automatically cache the dependency directories for several popular tools and frameworks to speed up future builds.

This means that all packages saved in these directories at the end of a build will be automatically loaded on the build machine for future builds.

Packages in the following directories will be automatically cached:

- `node_modules`
- `clone/node_modules-cache`
- `.virtualenv/bin/`
- `.virtualenv/lib/python2.7/site-packages`
- `.m2/repository`
- `clone/tmp/parallel_runtime_cucumber.log`
- `.ivy2`

## Clearing The Cache

You can manually clear the cache either by removing the populated cache directory in your setup commands at the start of your build (for instance, by adding a startup command `rm -rf node_modules`) or by clicking on **Reset Dependency Cache** on the right sidebar when viewing any build.

![Clearing the dependency cache]({{ site.baseurl }}/images/continuous-integration/clear_cache.png)

## Support

As always, feel free to contact [<EMAIL>](mailto:<EMAIL>) if you have any questions.<commit_msg>adding cs clear-cache<commit_after>---
title: Dependency Cache on Codeship Basic
weight: 85
tags:
  - cache
  - dependencies
category: Getting Started
---

<div class="info-block">
Note that this article addresses caching on **Codeship Basic**. If you are looking for information on caching with **Codeship Pro**, [click here]({{ site.baseurl }}{% link _pro/getting-started/caching.md %})
</div>

## Automatic Dependency Caching

On all Codeship Basic projects, we automatically cache the dependency directories for several popular tools and frameworks to speed up future builds.

This means that all packages saved in these directories at the end of a build will be automatically loaded on the build machine for future builds.

Packages in the following directories will be automatically cached:

- `node_modules`
- `clone/node_modules-cache`
- `.virtualenv/bin/`
- `.virtualenv/lib/python2.7/site-packages`
- `.m2/repository`
- `clone/tmp/parallel_runtime_cucumber.log`
- `.ivy2`

## Clearing The Cache

You can manually clear the cache either by removing the populated cache directory in your setup commands at the start of your build (for instance, by adding a startup command `rm -rf node_modules`), by using our custom `cs clear-cache` command in your startup commands or by clicking on **Reset Dependency Cache** on the right sidebar when viewing any build.

![Clearing the dependency cache]({{ site.baseurl }}/images/continuous-integration/clear_cache.png)

## Support

As always, feel free to contact [<EMAIL>](mailto:<EMAIL>) if you have any questions.
{'fraction_non_alphanumeric': 0.0909688013136289, 'fraction_numerical': 0.003940886699507389, 'mean_word_length': 4.682835820895522, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5383976', 'n_tokens_mistral': 856, 'n_tokens_neox': 815, 'n_words': 372}