This ensures that option expressions are resolved in the project
level overrides before attempting to composite them on the instantiated
elements. Seems this is a regression from introducing the include
directive.

This fixes issue #658

This is a regression test for issue #658

Fix override options

Closes #658

See merge request !802

Since ArtifactCache.setup_remotes() can be expensive and should only
happen once, this commit will assert() if it is called a second time
on an artifact cache instance.

Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>

The initialization of remotes is done by ArtifactCache.setup_remotes()
and as such it was wrong for these tests to be calling
CASCache.initialize_remotes() a second time.

Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>

The SandboxRemote used to construct its own CASCache which was
considered dangerous.  This patch replaces that with acquisition of
the cache via the Platform singleton, hopefully eliminating issues
from having more than one artifact cache object in a single process.

Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>

sandbox/_sandboxremote.py: Acquire cache via Platform

See merge request !797

When configuring a push remote and specifying either the client-cert
or the client-key, then both must be specified. This ensures we
get an informative error instead of a stack trace and BUG.

Fixes issue #625

Test that we get the expected error when configuring a client-cert
without client-key, or the inverse.

Fix artifact config crash

Closes #625

See merge request !804

richardmaw-codethink authored Sep 04, 2018 and Tristan Van Berkom committed Sep 18, 2018

This fixes all devices being mapped to the non-existant device 0,
which prevents being able to use even safe devices like /dev/null
through the hardlinks FUSE layer.

richardmaw-codethink authored Sep 04, 2018 and Tristan Van Berkom committed Sep 18, 2018

This is needed to permit access to the device nodes added to /dev
on Linux when FUSE is used as root.

The chroot sandbox only works with all privileges,
so there's no explicit check for being root
or having the appropriate capabilities.

A check for whether it's running as root isn't needed on Linux with bubblewrap
because /dev or its devices are mounted on top of the FUSE layer,
so device nodes are accessed directly rather than through the FUSE layer.

fix chroot sandbox devices

See merge request !781

The code was creating the cwd folder but when the workspace was
mounted in to the buildroot it was hiding the folder created in it
behind the bind mounted workspace.

However buy using the bubble warp `--dir` directive to ensure that cwd
exists then we can cover both workspace and non workspace situation with
the same method.

Build stream was only creating command-subdir for non workspace builds
this has now been fixed, and this regression test should support the
feature.

Adding the conf-root variable makes creating out of source builds
slightly easier.

Three examples covering out of source builds for:
 * basic autotools
 * basic cmake
 * autotools from a folder inside the source folder

This is also the first cmake example.