| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This will allow all users to not have to care about whether the option
is expanded or not, making it easier to use variables everywhere
|
|
|
|
|
| |
The pip element was copied already to bst-plugins-experimental.
We don't need to have two copies of it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mostly a semantic change which defines how deprecation warnings
are suppressed in a more consistent fashion, by declaring such suppressions
in the plugin origin declarations rather than on the generic element/source
configuration overrides section.
Other side effects of this commit are that the warnings have been enhanced
to include the provenance of whence the deprecated plugins have been used in
the project, and that the custom deprecation message is optional and will
appear in the message detail string rather than in the primary warning text,
which now simply indicates that the plugin being used is deprecated.
Documentation and test cases are updated.
This fixes #1291
|
|
|
|
|
|
|
| |
Part of https://gitlab.com/BuildStream/buildstream/-/issues/1068.
Make behavior of `shell` command similar to other commands that need
sources like `build`, `workspace open`, `source checkout` etc.
|
| |
|
| |
|
|
|
|
| |
This is no longer needed now that we support caching buildtrees in CAS.
|
| |
|
|
|
|
|
|
|
|
|
| |
Unfortunately the options from main project cannot always be processed
in the include processing since project configuration might load
option declarations from a separate file. For that reason the result
of `Include.process` should still be passed through the option
processor. But all options files included from junctioned are already
evaluated.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This includes adding an entry for the recursive submodules changes from !1765,
and adding myself to the authors of _gitsourcebase.py.
|
|
|
|
| |
Prepare for next release.
|
| |
|
| |
|
| |
|
|
|
|
| |
Also highlight the change & configuration in NEWS
|
|
|
|
|
|
|
|
|
|
|
| |
This runs two versions of the plugins:
- The latest stable is not allowed failures and is run on every platform
- The master version is allowed failure, and only runs on a single
architecture
This also adds a new entrypoint to register source tests to run against
BuildStream.
|
|
|
|
|
| |
Instead output "junction" in magenta for info. Also include test
in format/junctions.py
|
| |
|
|
|
|
|
| |
We don't have many of the `--track` options anymore, so we can remove
handling for them in parts of the code that don't need it.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Prepare NEWS file for next development snapshot release. There hasn't
been any breaking changes since last snapshot.
|
| |
|
| |
|
|
|
|
| |
Add a placeholder section to hold newsworthy items for the next release.
|
|
|
|
|
| |
Since we decided to release the snapshot version '1.91.0', this patch
updates the version information in the NEWS entry accordingly.
|
|
|
|
|
| |
Since the majority of the NEWS entries seem to be written in the past
tense, change the handful of entries that aren't.
|
|
|
|
|
|
|
|
| |
This was incorrectly copy-pasted in the wrong location.
See
https://gitlab.com/BuildStream/buildstream/commit/108a38edd86d9de3ef0ce78cb005041662ed279e#note_216141606
for related discussion.
|
|
|
|
|
|
| |
The current mentions of `source checkout` in the NEWS file
have been updated so that they explain the recent changes to
`bst source checkout`
|
|
|
|
|
|
|
|
|
|
|
| |
Since the development branch of BuildStream hasn't had a release in a
while, the number of entries in the NEWS file is rather large. So, to
make it easier to digest, split it into topics like CLI, API, Plugins
etc.
Under each topic, I have attempted to sort entries by their severity.
Despite being long, the list is quite likely still incomplete.
|
|
|
|
|
|
|
|
|
| |
--long or -l will provide the user with extra information about the
contents of the artifacts, including permission mode, file type, size
and name. In order for this to work, the way in which list-contents
works has been modified.
A test and NEWS entry have also been added within this commit
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
this commit introduces the bst artifact list-contents
command. When used it provides the user with a list of
the contents within the artifact.
Tests and a NEWS entry have also been added for the command.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Calling runcli with project set to None results in
setting the directory to the string 'None'.
Instead, only set it when the given project argument is not None.
|
|
|
|
|
| |
Also update documentation in plugin for APIs that do accept Node and
not `dict`.
|
|
|
|
|
|
|
|
|
|
|
| |
Calls to `isinstance` can be particularily costly. Using type() is
much faster. The only known case where the `isinstance` was useful
is for dictionnaries where we would ask for a 'Mapping' instead.
Disallowing 'Mapping' for expected_type considerably speeds up the
calls to this functions.
Also add into NEWS
|
|
|
|
|
|
|
|
| |
This will replace the previous use of a directory structure.
Quite a lot is changed here, predominantly _artifact and _artifactcache
modules.
Part of #974
|
| |
|
| |
|
|
|
|
|
|
| |
This is a follow-up to !1257 - YAML New World Order.
Now that !1257 has landed, plugin's *must* use the Plugin.node_*
family of functions to access or modify node members.
|