From 070d053e5cc47e572e9f9e647315082bd7a15c63 Mon Sep 17 00:00:00 2001
From: Chandan Singh <csingh43@bloomberg.net>
Date: Wed, 24 Apr 2019 22:53:19 +0100
Subject: Move source from 'buildstream' to 'src/buildstream'

This was discussed in #1008.

Fixes #1009.
---
 src/buildstream/data/userconfig.yaml | 113 +++++++++++++++++++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 src/buildstream/data/userconfig.yaml

(limited to 'src/buildstream/data/userconfig.yaml')

diff --git a/src/buildstream/data/userconfig.yaml b/src/buildstream/data/userconfig.yaml
new file mode 100644
index 000000000..34fd300d1
--- /dev/null
+++ b/src/buildstream/data/userconfig.yaml
@@ -0,0 +1,113 @@
+# Default BuildStream user configuration.
+
+#
+#    Work Directories
+#
+#
+# Note that BuildStream forces the XDG Base Directory names
+# into the environment if they are not already set, and allows
+# expansion of '~' and environment variables when specifying
+# paths.
+#
+
+# Location to store sources
+sourcedir: ${XDG_CACHE_HOME}/buildstream/sources
+
+# Root location for other directories in the cache
+cachedir: ${XDG_CACHE_HOME}/buildstream
+
+# Location to store build logs
+logdir: ${XDG_CACHE_HOME}/buildstream/logs
+
+# Default root location for workspaces, blank for no default set.
+workspacedir: .
+
+#
+#    Cache
+#
+cache:
+  # Size of the artifact cache in bytes - BuildStream will attempt to keep the
+  # artifact cache within this size.
+  # If the value is suffixed with K, M, G or T, the specified memory size is
+  # parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base
+  # 1024), respectively.
+  # Alternatively, a percentage value may be specified, which is taken relative
+  # to the isize of the file system containing the cache.
+  quota: infinity
+
+  # Whether to pull build trees when downloading element artifacts
+  pull-buildtrees: False
+
+  # Whether to cache build trees on artifact creation:
+  #
+  #  always  - Always cache artifact build tree content
+  #  auto    - Only cache build trees when necessary, e.g., for failed builds
+  #  never   - Never cache artifact build tree content. This is not recommended
+  #            for normal users as this breaks core functionality such as
+  #            debugging failed builds and may break additional functionality
+  #            in future versions.
+  #
+  cache-buildtrees: auto
+
+
+#
+#    Scheduler
+#
+scheduler:
+
+  # Maximum number of simultaneous downloading tasks.
+  fetchers: 10
+
+  # Maximum number of simultaneous build tasks.
+  builders: 4
+
+  # Maximum number of simultaneous uploading tasks.
+  pushers: 4
+
+  # Maximum number of retries for network tasks.
+  network-retries: 2
+
+  # What to do when an element fails, if not running in
+  # interactive mode:
+  #
+  #  continue  - Continue queueing jobs as much as possible
+  #  quit      - Exit after all ongoing jobs complete
+  #  terminate - Terminate any ongoing jobs and exit
+  #
+  on-error: quit
+
+
+#
+#    Logging
+#
+logging:
+
+  # The abbreviated cache key length to display in the UI
+  key-length: 8
+
+  # Whether to show extra detailed messages
+  verbose: True
+
+  # Maximum number of lines to print from the
+  # end of a failing build log
+  error-lines: 20
+
+  # Maximum number of lines to print in a detailed
+  # message on the console or in the master log (the full
+  # messages are always recorded in the individual build
+  # logs)
+  message-lines: 20
+
+  # Whether to enable debugging messages
+  debug: False
+
+  # Format string for printing the pipeline at startup, this
+  # also determines the default display format for `bst show`
+  element-format: |
+
+    %{state: >12} %{full-key} %{name} %{workspace-dirs}
+
+  # Format string for all log messages.
+  message-format: |
+
+    [%{elapsed}][%{key}][%{element}] %{action} %{message}
-- 
cgit v1.2.1