You will need about one minute to read this article.
This article addresses caching on CodeShip Basic. There is a separate guide for caching on CodeShip Pro.
On all CodeShip Basic projects, we automatically cache the dependency directories for several popular tools 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.
Any packages, up to 500mb, in the following directories at the end of your build will be automatically cached:
We automatically configure
bundler to write to
pip to write to
yarn to write to
You can manually clear the dependency cache in several different ways:
cs clear-cachecommand at the start of your setup commands to clear everything under
rm -rf node_modules.
If you want to cache items in your build that are not already handled in the automatic configurations above you can also manually cache items. If the tool you are using provides a way to set a cache location, perhaps with an environment variable, you can point it to the
Otherwise you can manually copy items to
$HOME/cache at the end of the build and then at the start of the build you can either copy them back out of the cache or create a symlink to the cached location.
Contact our support team or post on Stack Overflow using the tag
#codeship. Did you check the status page and changelog?
There are also several code examples and sample projects available for you to get started with.