If a cached artifact is available, it will be downloaded by build workers, put into place, and our default will be skipped. If a cached artifact isn’t available, dependency install will happen from scratch.When a session completes, including any post-build hooks, the contents of the saved directories will be written into off-worker storage and tracked for the next build.
These package installs often take several minutes – time that you don’t want to be wasting on every single build.
Solano CI will keep its cache until one or more of these manifest files in your repo changes.
You can also use the “Build Now (Drop Cache)” menu item from a report page, which will also trigger a new build.
We are preparing a UI and a CLI to let you invalidate without making a commit or triggering a build.
There are some subtleties here though, in Circle CI 1.0 we create a read-only BTRFS snapshot, and save caches from these.
If there are any symlinks that point outside of the snapshot, then they will not be cached, since BTRFS snapshots do not recursively follow symlinks.Normally a cache object will always be used if one is found.To test a build without a cache uou can use the “Build Now (Ignore Cache)” menu item from a report page, which will also trigger a new build. However the option does not invalidate the cache so it will still be able to be used in future builds.When a manifest file changes, the cache will be invalidated and a new install will happen automatically for When your build starts, after Solano CI pulls your repo from your git server, our system will compute a cache key based on the configured key files (or our defaults).You will see a message displayed in the build report page indicating the files checked and the keys we computed.Each branch of your project will have a separate cache.