| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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.
|
| |
|
|
|
| |
Caching buildtrees may significantly increase CAS disk usage. Change the
default to cache buildtrees only when required for core functionality.
|
| |
|
|
|
|
|
|
|
|
| |
We anticipate other cases than build failures where buildtree caching
will be required. E.g., incremental workspace build with remote
execution. Or running tests in a buildtree in parallel with the build of
reverse dependencies.
This renames the option value 'failure' to the more generic 'auto' to
cover these other cases as well.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This allows use of variables such as %{prefix} and matches the
documentation. This is a breaking change.
Fixes #721
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Artifacts can be cached explicitly with an empty `build tree` when
built via the cli main options or user config for all or only
successful build artifacts. Default behaviour is to still create
and cache all expected buildtrees.
element.py: _cache_artifact() Check if context for cache_buildtrees
has been set to always or failure with a corresponding build
result, if not skip attempting to export the build-root. Element
types without a build-root are cached with an empty buildtree
regardless. Update _stage_sources_at() to warn the user that the
buildtree import is empty.
tests/integration: Add test to artifact.py for the optional caching
of buildtree content from bst build. Rename build-tree.py to
shellbuildtrees.py to reflect included test cases, add test for
empty buildtree warning and failure option.
NEWS: Add entry for new option.
|
| |
|
|
|
|
| |
Providing a remote will limit build's pull/push remote actions to
the given remote specifically, ignoring those defined via user or
project configuration.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a breaking change, as it affects behaviour that people might be
relying on. An entry has been added to NEWS.
As proposed on the mailing list, this change removes the unconditional
prompts on:
o: bst workspace reset
o: bst workspace close --remove-dir
If interactive, these commands would always interrupt you with a prompt
like this:
This will remove all your changes, are you sure?
This seems like it may just save someone's work some time. It may also
condition folks to hit 'y' quickly without thinking.
This change also makes the non-interactive behaviour consistent with the
interactive behaviour in the default case. There is also the case of the
prompt configured by 'really-workspace-close-project-inaccessible',
which may be tackled in later work.
This change also removes the new config options to suppress those
prompts, and their associated news entry.
The relevant bit of the mailing list conversation is here:
https://mail.gnome.org/archives/buildstream-list/2018-December/msg00106.html
The issue to make interactive and non-interactive behaviour consistent
is here:
https://gitlab.com/BuildStream/buildstream/issues/744
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the event that the project could not be found, stop BuildStream from
asking if the user would like to create a new project. Exit with error
instead, and give a hint to the user in case they're new.
As proposed on the mailing list here:
https://mail.gnome.org/archives/buildstream-list/2018-December/msg00082.html
The new interaction looks like this:
$ bst show nonsuch.bst
No project found. You can create a new project like so:
bst init
Error loading project: None of ['project.conf', '.bstproject.yaml']
found in '/src/temp/blah' or any of its parent directories
Fixes #826
|
| |
|
|
|
|
| |
Also, change the existing entry about `source-checkout` to be
`source checkout` instead. And, while we are there, move it near the
other announcements about the source command group.
|
| | |
|
| | |
|
| |
|
|
| |
This is a part of #222
|
| |
|
|
| |
This is a part of #222
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
