diff options
author | Tom Pollard <tom.pollard@codethink.co.uk> | 2018-11-05 13:32:29 +0000 |
---|---|---|
committer | Jürg Billeter <j@bitron.ch> | 2018-11-17 13:07:59 +0000 |
commit | 454dcaf1152b21657702af593c052f7ab90333a1 (patch) | |
tree | 30ed236c0f5b9104bd87b6220272003bb123268f /NEWS | |
parent | 199bfff16160cd0c7c0fe56af3723656f6148068 (diff) | |
download | buildstream-454dcaf1152b21657702af593c052f7ab90333a1.tar.gz |
Don't pull artifact build trees by default.tpollard/494
The addition of cached build trees being included in element
artifacts has led to mostly redundant download overheads when
pulling from a remote artifact server. As such the default behaviour
of pull shouldn't fetch the build tree object if available.
element.py: extend relevant pull logic for specified subdir
consideration and ensure push logic does not lead to partial
artifact pushes. Change assumption that the buildtree can be
extracted if artifact is cached. __cached_buildtree() and
__pull_directories() helpers added.
_artifactcache/: artifactcache.py & cascache.py inclusion of
helper functions for subdir artifact checking & fetching, fetch
logic extended to only pull required artifact directories.
extract & checkout updated to handle full/partial operation.
tests/: addition of integration test pullbuildtrees.py,
buildtrees.py adapted cli options, testutils/artifactshare.py
has_artifact changed to return artifact digest on true condition.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 14 |
1 files changed, 12 insertions, 2 deletions
@@ -38,13 +38,23 @@ buildstream 1.3.1 a bug fix to workspaces so they can be build in workspaces too. o Creating a build shell through the interactive mode or `bst shell --build` - will now use the cached build tree. It is now easier to debug local build - failures. + will now use the cached build tree if available locally. It is now easier to + debug local build failures. o `bst shell --sysroot` now takes any directory that contains a sysroot, instead of just a specially-formatted build-root with a `root` and `scratch` subdirectory. + o Due to the element `build tree` being cached in the respective artifact their + size in some cases has significantly increased. In *most* cases the build trees + are not utilised when building targets, as such by default bst 'pull' & 'build' + will not fetch build trees from remotes. This behaviour can be overridden with + the cli main option '--pull-buildtrees', or the user configuration cache group + option 'pull-buildtrees = True'. The override will also add the build tree to + already cached artifacts. When attempting to populate an artifactcache server + with cached artifacts, only 'complete' elements can be pushed. If the element + is expected to have a populated build tree then it must be cached before pushing. + ================= buildstream 1.1.5 |