| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
"Ignore submodule" sounds like it could be an action, so this changes the name
to more clearly be a predicate.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, GitSourceBase would only consider immediate submodules of the
superproject. It now fetches and stages recursively.
To achieve this, this commit somewhat refactors the relationship between
GitMirror and GitSourceBase. Enumerating GitMirrors for the submodules is now
done in GitMirror itself. GitSourceBase recursively iterates these mirror
classes with _recurse_submodules and applies the source configuration with
_configure_submodules.
|
| |
|
|\
| |
| |
| |
| | |
Small cleanups in `element._fetch`
See merge request BuildStream/buildstream!1768
|
| | |
|
|/
|
|
|
| |
This variable is used only once, when the original is used multiple
times. This only increases the cognitive load
|
|\
| |
| |
| |
| | |
job.py: Replace message queue with pipe
See merge request BuildStream/buildstream!1766
|
|/
|
|
|
|
|
|
| |
A lightweight unidirectional pipe is sufficient to pass messages from
the child job process to its parent.
This also avoids the need to access the private `_reader` instance
variable of `multiprocessing.Queue`.
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Use latest freedesktop-sdk 19.08.5
See merge request BuildStream/buildstream!1762
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Add CI job to test buildbox-run-bubblewrap and buildbox-fuse
Closes #1226
See merge request BuildStream/buildstream!1752
|
| | |
|
| |
| |
| |
| | |
Replaced by buildbox-run.
|
| |
| |
| |
| | |
Replaced by buildbox-run.
|
| |
| |
| |
| | |
This job uses buildbox-run-bubblewrap and buildbox-fuse.
|
| |
| |
| |
| |
| | |
This updates buildbox-common and builbox-casd to 0.0.5 and adds
buildbox-fuse and buildbox-run-bubblewrap.
|
|/ |
|
|\
| |
| |
| |
| | |
tox.ini: Add ability to run tests in a randomized order
See merge request BuildStream/buildstream!1760
|
|/
|
|
|
|
|
|
|
|
| |
Also register them to run nightly.
Running tests in a randomized order is a good way of checking whether
our tests depend on each others or not.
Since we order them globally, tests will take longer to run, but that
will give us higher confidence that they are correct.
|
|\
| |
| |
| |
| | |
tests/sources/tar.py: `utils._force_rmtree` instead of giving 777 permissions
See merge request BuildStream/buildstream!1763
|
|/
|
|
|
|
|
|
|
| |
While this is deep in our test suite, and should therefore never
create files that leak information, our code security linter
complains about setting broad file permissions.
We should really be using `utils._force_rmtree` here anyway, to stop
duplicating code, so that's what we do.
|
|\
| |
| |
| |
| | |
Add buildbox-run sandboxing backend
See merge request BuildStream/buildstream!1738
|
| |
| |
| |
| | |
Individual commands are not logged with command batching.
|
| |
| |
| |
| | |
Individual commands are not logged with command batching.
|
| |
| |
| |
| | |
Individual commands are not logged with command batching.
|
| |
| |
| |
| | |
Logging differs with command batching.
|
| |
| |
| |
| | |
Bind mounting is not supported.
|
| |
| |
| |
| | |
The root directory can't be marked read-only with buildbox-run.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The purpose of the test is to ensure POSIX shared memory objects are
supported in the sandbox. On Linux this requires /dev/shm to be a tmpfs.
However, this should be supported by any full featured sandbox.
|
| |
| |
| |
| |
| | |
The buildbox-run sandbox is used only if BST_FORCE_SANDBOX is set to
buildbox-run.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
_project.py: Allow junctions to use parent remote when `ignore-junction-remotes` set
See merge request BuildStream/buildstream!1759
|
| |
| |
| |
| |
| |
| | |
Makes sure that `cache-junction-elements` and `ignore-junction-remotes`
work together correctly, and that setting `ignore-junction-remotes`
doesn't just remove all remote caches.
|
|/
|
|
|
|
|
|
|
|
|
|
| |
At present it doesn't seem to be possible to use ignore-remote-caches
and also cache cross-junction artifacts in one's own cache. By passing
the parent caches to the junction we ensure that things get cached in
the parent cache.
For a motivating purpose, consider that one may have a (patched)
junction which specifies a cache incompatible with master. This will
throw warnings at every invokation of bst, or you won't cache
cross-junction artifacts.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
'1211-stop-using-non-posix-features-in-small-test-suite-tests-to-avoid-fake-test-failures' into 'master'
Resolve "Stop using non-POSIX features in small test suite tests to avoid fake test failures"
Closes #1211
See merge request BuildStream/buildstream!1725
|
|/ |
|
|\
| |
| |
| |
| | |
man/bst-workspace-reset.1: Update workspace re-open help message
See merge request BuildStream/buildstream!1723
|
|/
|
|
| |
This was missed in !1710.
|
|\
| |
| |
| |
| | |
remove unused functions 1/2
See merge request BuildStream/buildstream!1753
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|