summaryrefslogtreecommitdiff
path: root/doc/source/cachekeys.rst
diff options
context:
space:
mode:
authorJames Ennis <james.ennis@codethink.com>2018-04-17 09:46:30 +0100
committerTristan Van Berkom <tristan.van.berkom@gmail.com>2018-04-17 16:52:27 +0000
commit58f8e6bc6de85247b4d84533036eb22a0b8ce497 (patch)
tree1902949c325b66755020068065c27b140479c7de /doc/source/cachekeys.rst
parent02119f198cc0ada3c8a927cb96f825a6ac519c5f (diff)
downloadbuildstream-58f8e6bc6de85247b4d84533036eb22a0b8ce497.tar.gz
Consistent titling
Diffstat (limited to 'doc/source/cachekeys.rst')
-rw-r--r--doc/source/cachekeys.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/source/cachekeys.rst b/doc/source/cachekeys.rst
index 4458d8883..f0df796c5 100644
--- a/doc/source/cachekeys.rst
+++ b/doc/source/cachekeys.rst
@@ -2,7 +2,7 @@
.. _cachekeys:
-Cache Keys
+Cache keys
==========
Cache keys for artifacts are generated from the inputs of the build process
@@ -19,7 +19,7 @@ includes:
* Dependencies (depending on cache key type, see below)
* Public data
-Cache Key Types
+Cache key types
---------------
There are two types of cache keys in BuildStream, ``strong`` and ``weak``.
@@ -42,7 +42,7 @@ or the environment changes but it will not change when a dependency is updated.
For elements without build dependencies the ``strong`` cache key is identical
to the ``weak`` cache key.
-Strict Build Plan
+Strict build plan
-----------------
This is the default build plan that exclusively uses ``strong`` cache keys
for the core functionality. An element's cache key can be calculated when
@@ -60,7 +60,7 @@ and non-strict build plans. If the artifact cache already contains an
artifact with the same ``weak`` cache key, it's replaced. Thus, non-strict
builds always use the latest artifact available for a given ``weak`` cache key.
-Non-strict Build Plan
+Non-strict build plan
---------------------
The non-strict build plan disables the time-consuming automatic rebuild of
reverse dependencies at the cost of dropping the reproducibility benefits.