| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
NEWS: Updating news for 1.93.3 snapshot.
See merge request BuildStream/buildstream!1891
|
|/ |
|
|\
| |
| |
| |
| | |
Plugin loading refactor, implement BST_MIN_VERSION
See merge request BuildStream/buildstream!1885
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The BST_MIN_VERSION guards assert that the BuildStream core which
loaded the plugin is compatible with the plugin itself.
This commit adds BST_MIN_VERSION to the base plugin.py with documentation
informing Plugin authors how to set the minimum version, and also adds
the assertions at plugin loading time in pluginfactory.py.
This commit also:
* Adds the BST_MIN_VERSION specification to all current core plugins
* Adds the BST_MIN_VERSION specification to plugins used in test cases
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test tests some of the basic failure modes of plugin loading,
which used to be written as internal tests but is not implemented
as a proper end-to-end test.
This commit also adds some machine readable reason codes to
pluginfactory.py so that we can assert the errors more specifically.
|
| |
| |
| |
| |
| | |
Before adding more tests to this directory, just making the directory
match more the structure of other test directories.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Plugin format versioning was decided to be removed for local
plugins and any plugins for which we do not load an explicitly
provided plugin. For pip, this will be handled with a standard
distutils/setuptools approach, allowing users to specify pip
style version boundaries in the plugin origins.
This patch refactors plugin loading so that all related code
goes into the private _pluginfactory module, a new small
PluginOrigin type was added to better manipulate loaded
origins.
Test cases have been removed and will be readded in a following
commit, adjusted to new expectations.
|
|\
| |
| |
| |
| |
| |
| | |
Switch preferred sandbox from bwrap to buildbox-run
Closes #719
See merge request BuildStream/buildstream!1888
|
| |
| |
| |
| |
| | |
bwrap is no longer the default. This job makes sure that the bwrap code
keeps working.
|
| |
| |
| |
| | |
buildbox-run is now the default.
|
| |
| |
| |
| |
| | |
This also enables local builds on non-Linux platforms, if a buildbox-run
implementation is available.
|
| | |
|
| |
| |
| |
| | |
This fixes an isolation issue in the test suite.
|
|/
|
|
| |
The fuse3 package is required for buildbox-fuse on Debian.
|
|\
| |
| |
| |
| | |
Require virtual directory support for element plugins
See merge request BuildStream/buildstream!1887
|
| |
| |
| |
| | |
`Sandbox.get_directory()` no longer exists.
|
|/
|
|
| |
Require element plugins to use `Sandbox.get_virtual_directory()`.
|
|\
| |
| |
| |
| | |
Adding as_str too Mapping nodes
See merge request BuildStream/buildstream!1866
|
|/ |
|
|\
| |
| |
| |
| | |
Prepare 1.93.2 development snapshot
See merge request BuildStream/buildstream!1886
|
|/ |
|
|\
| |
| |
| |
| | |
storage: Improve Directory API
See merge request BuildStream/buildstream!1878
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This catches incorrect use of the `Directory` API.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Remove bst shell --sysroot
See merge request BuildStream/buildstream!1882
|
| | |
|
|/
|
|
| |
This is no longer needed now that we support caching buildtrees in CAS.
|
|\
| |
| |
| |
| | |
Replace format-version with min-version
See merge request BuildStream/buildstream!1881
|
| | |
|
| |
| |
| |
| | |
This replaces "format-version" documentation.
|
| |
| |
| |
| |
| |
| |
| | |
This will be done differently in BuildStream 2, as explained
in this email:
https://mail.gnome.org/archives/buildstream-list/2020-April/msg00017.html
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With BuildStream 2.0, we start with a fresh API, everything that
is present at the time of the 2.0 release can implicitly be considered
to be available since 2.0.
In the future, we will be expressing new API additions using the
min-version semantic versioning style instead of format version too
(so new YAML configurations will be expressed as "since: 2.2" and
so on).
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* "min-version" is specified as a <major>.<minor> point version
and uses the installed BuildStream version instead of having
a separate versioning number for the format.
* The presence of "format-version" is now used to indicate
that we might be loading a BuildStream 1 project.
* For now, where parsing the version at startup is concerned, and
also where `bst init` is concerned, we artificially bump the
detected BuildStream version to 2.0 if we detect a version < 2.0,
these exceptions can be removed once 2.0 is tagged and released.
Summary of changes:
_project.py: Now parse "min-version" and detect "format-version" to
warn about loading a BuildStream 1 project
_versions.py: Remove obsolete BST_FORMAT_VERSION numbers from here
data/projectconfig.yaml: Remove old "format-version" from defaults
utils.py: Added new private _parse_version() helper function, and another
_get_bst_api_version() to get an adjusted API version.
frontend/app.py, frontend/cli.py: Updated `bst init` implementation
testing (buildstream.testing): Updated testing utilities to generate
and use projects with min-version instead of format-version.
tests and examples: Updated to use min-version across the board.
|
|\
| |
| |
| |
| | |
Increase test timeouts
See merge request BuildStream/buildstream!1884
|
| |
| |
| |
| | |
CI runners sometimes need more time under load.
|
| |
| |
| |
| | |
CI runners sometimes need more time under load.
|
|/
|
|
| |
CI runners sometimes need more time under load.
|