| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
With the use of buildbox-run on all platforms, there is no longer any
platform-specific code in the Platform subclasses.
|
| |
|
|
|
|
|
| |
buildbox-run is the only local sandbox and there are no plans to add
other sandboxing backends in the future. New platforms can be supported
by new buildbox-run implementations without requiring any changes in
BuildStream.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It is always true.
|
| |
|
|
| |
Replaced by buildbox-run.
|
| |
|
|
|
| |
Without the SafeHardlinks FUSE filesystem there is no longer a need to
increase the open file limit.
|
| |
|
|
| |
FUSE is no longer a blocker.
|
| | |
|
| | |
|
| |
|
|
| |
The bwrap sandbox will be removed.
|
| | |
|
| |\
| |
| |
| |
| | |
Optimize variable flattening
See merge request BuildStream/buildstream!1949
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Verifying for variables (all used variables defined and no cycle) is
much faster than flattening them. It also uses much less memory. Only
`bst show -f "%{vars}"` requires to flatten all variables. For other
cases we can improve performance by only checking rather than
flattening.
Also flattening very nested variables could lead to very long lists of
empty strings. The memory usage for flattening could be a lot bigger
than the resulting value. Force flattening and caching every
variable definitions can improve intermediate memory consumption and
only consume memory of the size of the result.
Finally, an optimization allowed inifinite cycles leading to
segmentation fault. This was solved by simplifying the code.
|
| |\
| |
| |
| |
| | |
update FD overnights
See merge request BuildStream/buildstream!1953
|
| |/
|
|
| |
bst2 efforts are now concentrated on the `valentindavid/bst2` branch
|
| |\
| |
| |
| |
| | |
Add new core `link` element kind
See merge request BuildStream/buildstream!1948
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes:
* The `target` feature from the junction plugin
* Special case code in the loader for the `target` feature
* The `target` related cases in tests/format/junctions.py
This also adjusts the `target` related documentation in
the `junction` element to suggest using a `link` element for
the purpose of using a subproject junction configuration to
access a common sub-subproject.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This element acts as a symbolic link, it has no other configurations
other than to specify the element (or junction) to which it refers to,
either in the local project or in a subproject.
|
| |/
|
|
|
| |
Within the _loader module, the LoadElement will need to use this
in order to resolve links.
|
| |\
| |
| |
| |
| | |
_loader/loader.py: Remove useless line of code.
See merge request BuildStream/buildstream!1946
|
| |/
|
|
|
|
|
|
|
| |
We were redundantly calling Loader._load_file() directly
before calling Loader.get_loader(), even though Loader.get_loader()
implicitly loads the file anyway.
To pass tests, we needed to fix get_loader() to pass provenance
along to Loader._load_file().
|
| |\
| |
| |
| |
| | |
loader: removing the NO_PROGRESS object
See merge request BuildStream/buildstream!1947
|
| |/
|
|
|
|
|
|
|
|
|
| |
While adding a mock task object to track progress in some loader
tests in commit 17144d84c2b63daf6e3aa9b42c6c773f134e8660, a new
`_NO_PROGRESS` object was added as an explicit marker to denote
that progress information should not be reported.
This complicates the code, None should be a sufficient value
for not reporting progress, while still permitting mock task
objects to capture progress if desired.
|
| |\
| |
| |
| |
| | |
Support version specific configuration files
See merge request BuildStream/buildstream!1941
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
Allow users to keep separate buildstream.conf files in their
XDG_CONFIG_HOME for separate BuildStream versions, in case they
have BuildStream 1 and 2 installed.
Like other major version safeguards and warnings, this new
addition also supports future major versions if they should
appear.
|
| |\
| |
| |
| |
| |
| |
| | |
element.py: Always expand public data's variables
Closes #1310
See merge request BuildStream/buildstream!1943
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a bug introduced by d7d18c1a2e454c507afd9e1d3f1358639dd43871,
where public data integration commands and others would never get their
data expanded and would thus fail to run.
The previous however revelead a previous bug, where variables values in
public data of elements would not be part of the cache key of an element
or it's reverse dependencies, and thus, on variable change, rebuilds
would not happen when they would have been needed.
This ensures that all the public data is always resolved and part of the
element's cache key. This however will bring a rebuild of an element
whenever its integration commands variables change, which is simpler to
handle than to try to push that responsibility on reverse dependencies,
since public data can contain plugin-defined values.
|
| |\
| |
| |
| |
| | |
cascache.py: Drop unnecessary FindMissingBlobs from _send_directory()
See merge request BuildStream/buildstream!1944
|
| |/
|
|
|
|
| |
buildbox-casd `UploadMissingBlobs` will call `FindMissingBlobs` before
the actual upload. Having BuildStream call `FindMissingBlobs` as well
adds unnecessary overhead.
|
| |\
| |
| |
| |
| | |
.gitlab-ci.yml: Configure SAST analyzers
See merge request BuildStream/buildstream!1939
|
| |/
|
|
|
| |
Disable flawfinder and eslint jobs as this repository contains no C or
JavaScript code to be analyzed.
|
| |\
| |
| |
| |
| |
| |
| | |
element.py: Expand variables in sandbox config
Closes #1303
See merge request BuildStream/buildstream!1938
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
doc/source/format_declaring.rst: Fixing spelling mistake
See merge request BuildStream/buildstream!1940
|
| |/
|
|
|
| |
Making some examples more consistent with regards to indentation
of YAML, and fixing "recursice -> recursive" spelling mistake.
|
| |\
| |
| |
| |
| | |
Introduce new `junction` plugin origin
See merge request BuildStream/buildstream!1935
|
| | | |
|
| | | |
|
