# Using unified cache / Control cache identity

**URL:** <https://travis-ci.community/t/using-unified-cache-control-cache-identity/1531>\
**Category:** Feature Requests\
**Tags:** caching\
**Created:** [December 20, 2018, 8:08am UTC](https://travis-ci.community/t/using-unified-cache-control-cache-identity/1531 "2018-12-20T08:08:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [April 29, 2019, 1:55pm UTC](https://travis-ci.community/t/using-unified-cache-control-cache-identity/1531/3 "2019-04-29T13:55:40Z")

</div>

Explicitly specifying cache identity conflicts with the principle of build matrix.

Related: [Allow a next-stage job read-only access to the cache of a previous-stage one; or make exported/imported artifacts](https://travis-ci.community/t/allow-a-next-stage-job-read-only-access-to-the-cache-of-a-previous-stage-one-or-make-exported-imported-artifacts/905)

---

_[View the full topic](https://travis-ci.community/t/using-unified-cache-control-cache-identity/1531)._