setup.py: require ruamel.yaml >= 0.15.41 < 0.15.52

See merge request !975

f_bfree space might not be usable. In practice we see failures in big
disks because f_bfree is over 2GB and f_bavail is 0. We get ENOSPC if
writing on disk then.

We plan to make cache incomplete. That is some blobs are missing.  For
most of cases we will delete references when requested if they are
incomplete. But there will be corner cases where objects are removed
after the reference is requested.

The file is already a temporary file and does not need copy.  ENOSPC
is thrown during that copy in issue #609.

Fixes #678.

This locks the temporary object file so that cleanup does not need to
be done for every write.

This also remove references when some objects are missing. This is in
preparation for the move from reference to object garbage collection.

When there is less than 2GB left, it cleans up have 10GB available.
These values are configurable.

Cleaning up in parallel might slow down the cleaning process

Fix cleanup of cache in server when disk is full

Closes #678

See merge request !830

push_message and push_directory will both raise assertion failures if
they fail to send the digest to the server. Checking the digest
returned by each only tests that the content was hashed locally, which
cannot reasonably fail.

_sandboxremote.py: Remove unnecessary tests.

Closes #786

See merge request !976

Fixes #723.

Add support for .netrc in remote/tar/zip plugins

Closes #723

See merge request !908

Angelos Evripiotis authored Nov 29, 2018 and Jürg Billeter committed Nov 30, 2018

It seems that the regenerated man pages haven't been committed for some
time. Add them all in one lump now.

Had to manually strip the version number from the generated files.

Had to manually fix the NAME field of bst.1 to not be 'bst - None'.

Oddly had to invoke click-man directly in order to get the changes to
be applied, the usual setup.py route mentioned in contributing.rst
didn't work.

Eyeballed the result of invoking man on each of the commands, seems
good.

man/: update with changes since Apr 2018

See merge request !981

Tom Pollard authored Nov 28, 2018 and Jürg Billeter committed Nov 30, 2018

Adds helper function _buildtree_pull_required() to determine if a
pullqueue should be constructed, for commands outside of bst pull
and build where it is determined that an element's buildtree
artifact is to be required given the respective semantics and
config. Utilised in push() to attempt to mitigate skipping the push
of partial elements without the user having to have preceded it with
an explicit pull.

cli.py: Add new behaviour to push command description

element.py: Move _cached_buildtree() to be non local private method,
use _KeyStrength types to reduce duplication.

tests/integration/pullbuildtrees.py also updated to cover this
use-case.

_stream.py: Ability to pull missing buildtrees outside of pull/build

Closes #774

See merge request !978

_loader/loader.py: Added Suffix check and warning for named elements and add helper function

buildcheckout.py: Add mandatory .bst suffix tests
completions.py: Add test for fail on invalid suffix
Added required files for testing
integration/source-determinism.py: renamed test elements to end with .bst
loader/__init__.py: initialised context properly with load and a message handler

Mandatory .bst suffix

See merge request !967

This was previously missing, causing our CI to forget to rebuild the sessions
when updating the documentation.

This fixes issue #778

MANIFEST.in: Include the sources for rebuilding the documentation session HTML

Closes #778

See merge request !984

Chandan Singh authored Sep 26, 2018 and Benjamin Schubert committed Dec 03, 2018

Currently, `bst checkout --deps none` command always produces empty
output. Fix this issue and add regression test for the same.

- element_enums.py: Add Scope.NONE.

- element.py: Ensure Scope.NONE works correctly in addition to
  Scope.RUN/Scope.ALL in Element.dependencies() and Element.search().

- tests/frontend/buildcheckout.py: Fix tests for `--deps none`.

Fixes #670.

Chandan Singh authored Sep 21, 2018 and Benjamin Schubert committed Dec 03, 2018

As discussed in
https://mail.gnome.org/archives/buildstream-list/2018-September/msg00064.html,
add `--deps build` option to `bst checkout`. This will allow users to
checkout the all build dependencies of a given element using a single
command.

- _frontend/cli.py: Add `--deps build` option for `bst checkout`.

- element.py: Support `deps='build'` in Element._prepare_sandbox().

- tests/frontend/buildcheckout.py: Ensure `--deps build` works as
  expected.

Before we would have a intricate logics with multiple arguments
that might get ignored.

This simplifies the design and introduces a bool `shell` instead
of having two different variables concerned about scope

Add `--deps build` option to `bst checkout`

Closes #670

See merge request !819

Javier Jardón authored Dec 02, 2018 and Tristan Van Berkom committed Dec 03, 2018

See #783

git: warn about checkout submodules  by default

See merge request !983

i.e. with a given directory and filename, check parent directories until
either a directory with the filename is found, or you reach the root of
the filesystem.

This is a part of #222

WorkspaceProject contains all the information needed to refer back to a
project from its workspace (currently this is the project path and the
element used to create this workspace)

This is stored within a WorkspaceProjectCache object, which keeps
WorkspaceProjects around so they don't need to be loaded from disk
repeatedly.

This is a part of #222

This is a part of #222

This is a part of #222

Searching for the workspace file is preferred to searching for the
project file for the moment, because it avoids the circumstance of
the workspaces being inside a directory where a higher-level directory
may have project.conf (but may not be a buildstream project).

This is a part of #222

This is a part of #222

This is a part of #222

This is a part of #222

This is a part of #222

cli: Interactively warn if the user is trying to close the workspace they're using to load the project

This involves changes in:
* _stream.py:
  * Add the helper Stream.workspace_is_required()
* userconfig.yaml:
  * Add a default value for prompt.really-workspace-close-project-inaccessible
* _context.py:
  * Load the prompt 'really-workspace-close-project-inaccessible' from
    user config.
* cli.py:
  * If buildstream is invoked interactively, prompt the user to confirm
    that they want to close the workspace they're using to load this
    project.

This is a part of #222

This is a part of #222

This is a part of #222