summaryrefslogtreecommitdiff
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
...
* frontend: Remove build --all flag in favour of --deps all/plantmewett/build-deps-cliTom Mewett2019-08-281-0/+4
|
* NEWS: Add NEWS entry for bst artifact showjennis/bst_artifact_showJames Ennis2019-08-271-0/+5
|
* NEWS: Add NEWS entry following change in cache key calculationjennis/add_project_to_protoJames Ennis2019-08-191-0/+7
|
* Addition of bst artifact list-contents:Rebecca Grayson2019-08-161-0/+4
| | | | | | | 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.
* NEWS: Added a news entry announcing the two new junction config optionsJames Ennis2019-08-061-0/+8
|
* News: Added a news item for the new BuildBox sandboxbuildboxWilliam Salmon2019-07-251-0/+4
|
* NEWS: update for new Node APIBenjamin Schubert2019-07-151-14/+7
|
* runcli.py: Don't set project to 'None'AlexFazakas2019-07-021-0/+3
| | | | | | | 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.
* NEWS: restrict `Plugin.node_items` to be called on `Node`s.bschubert/stricter-node-apiBenjamin Schubert2019-06-071-0/+3
| | | | | Also update documentation in plugin for APIs that do accept Node and not `dict`.
* _yaml.pyx: Forbid expected_type=Mapping, and remove isinstance checkBenjamin Schubert2019-06-031-0/+3
| | | | | | | | | | | 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
* _artifact.py: Rework to use artifact protoRaoul Hidalgo Charman2019-05-151-0/+6
| | | | | | | | This will replace the previous use of a directory structure. Quite a lot is changed here, predominantly _artifact and _artifactcache modules. Part of #974
* Remove OSTree plugin; It lives now in the bst-plugins-experimental repoJavier Jardón2019-05-141-0/+3
|
* NEWS: Add entry about junction targetsChandan Singh2019-04-181-0/+3
|
* NEWS: Add YAML New World Order entryJames Ennis2019-03-291-0/+8
| | | | | | 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.
* Change default of cache-buildtrees option to 'auto'Jürg Billeter2019-03-161-1/+1
| | | | | Caching buildtrees may significantly increase CAS disk usage. Change the default to cache buildtrees only when required for core functionality.
* Rename cache-buildtrees option value 'failure' to 'auto'Jürg Billeter2019-03-161-1/+1
| | | | | | | | | | 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.
* NEWS: Add news entry for bst artifact deleteJames Ennis2019-03-131-0/+4
|
* NEWS: Cross-junction dependencies can now be specified inlineChandan Singh2019-02-261-0/+3
|
* element.py: Expect absolute paths in overlap whitelistsValentin David2019-02-191-0/+3
| | | | | | | This allows use of variables such as %{prefix} and matches the documentation. This is a breaking change. Fixes #721
* NEWS: Add entry for change in symlink handlingJürg Billeter2019-02-141-0/+4
|
* Provide configuration for the optional creation of buildtreestpollard/896Tom Pollard2019-02-131-0/+8
| | | | | | | | | | | | | | | | | | | | | 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.
* Add --remote, -r option to bst build, inline with pull & pushTom Pollard2019-02-051-0/+4
| | | | | | Providing a remote will limit build's pull/push remote actions to the given remote specifically, ignoring those defined via user or project configuration.
* BREAK:remove unconditional 'are you sure?' promptsAngelos Evripiotis2019-01-291-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* news: fix 'osbolete' spellingAngelos Evripiotis2019-01-281-1/+1
|
* NEWS: Add entry for default target featurePhillip Smyth2019-01-241-0/+4
|
* Add NEWS entry describing the deprecation of checkout, pull and pushJames Ennis2019-01-221-0/+10
|
* BREAK: remove auto-init behaviourAngelos Evripiotis2018-12-201-2/+8
| | | | | | | | | | | | | | | | | | | | | 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
* NEWS: Add entry for new source command groupChandan Singh2018-12-141-2/+6
| | | | | | 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.
* NEWS: Mention `bst artifact log`Richard Maw2018-12-121-0/+2
|
* NEWS: Add entry about the removal of source-bundle commandphil/source-checkout-optionsPhil Dawson2018-12-121-0/+6
|
* Add NEWS for guessing the element in commandsJonathan Maw2018-12-111-0/+5
| | | | This is a part of #222
* NEWS: Add an entry for being able to run commands from a workspacejonathan/workspace-fragment-createJonathan Maw2018-12-111-0/+4
| | | | This is a part of #222
* NEWS: Update for removal of default strip-commandsJavier Jardón2018-12-091-0/+4
|
* NEWS: Add news about broken 'git describe' by default.Valentin David2018-12-051-0/+4
|
* NEWS: Added update about the Mandatory .bst changePhillip Smyth2018-11-301-0/+4
|
* NEWS: Add entry for command batchingJürg Billeter2018-11-271-0/+3
|
* Added a news item for workspace open changesWilliam Salmon2018-11-211-0/+4
|
* Add prompt.workspace-... optionsAngelos Evripiotis2018-11-201-3/+5
| | | | | | | | | | Provide options in project.conf to disable the 'Are you sure ...' prompts when making destructive changes: - Add prompt.really-workspace-close-remove-dir - Add prompt.really-workspace-reset-hard Add a NEWS item for these.
* Add prompt.auto-init buildstream.conf optionAngelos Evripiotis2018-11-201-0/+4
| | | | | | | | | | | | | | | Provide an option in buildstream.conf to disable the 'Would you like to ...' prompt when we cannot resolve a project. Some users prefer not to be interrupted by such prompts, so pave the way to creating options to disable all those that might get in the way. Follow the example of the advice.* options 'git-config', and create a namespace for these UI options grouped by behaviour, rather than an over-reaching 'ui.*' namespace. In later work perhaps we'll also add 'advice.*' options. Add a NEWS item for this.
* NEWS: Add entry for the new source-checkout commandChandan Singh2018-11-191-0/+2
| | | | | | `bst source-checkout` command was recently added in https://gitlab.com/BuildStream/buildstream/merge_requests/820. Add a NEWS entry for the new command.
* Don't pull artifact build trees by default.tpollard/494Tom Pollard2018-11-171-2/+12
| | | | | | | | | | | | | | | | | | | | | | The addition of cached build trees being included in element artifacts has led to mostly redundant download overheads when pulling from a remote artifact server. As such the default behaviour of pull shouldn't fetch the build tree object if available. element.py: extend relevant pull logic for specified subdir consideration and ensure push logic does not lead to partial artifact pushes. Change assumption that the buildtree can be extracted if artifact is cached. __cached_buildtree() and __pull_directories() helpers added. _artifactcache/: artifactcache.py & cascache.py inclusion of helper functions for subdir artifact checking & fetching, fetch logic extended to only pull required artifact directories. extract & checkout updated to handle full/partial operation. tests/: addition of integration test pullbuildtrees.py, buildtrees.py adapted cli options, testutils/artifactshare.py has_artifact changed to return artifact digest on true condition.
* BREAK: manual.yaml: don't set any default env varsAngelos Evripiotis2018-11-011-0/+6
| | | | | | | | | | | | | | | | Remove the 'MAKEFLAGS' and 'V' defaults. Now that there is a specialised 'make' element, these make-specific defaults don't make sense here. This element is meant to be a blank slate for folks to build on. Note that this is a breaking change, that will require some users to make changes to their .bst files if they are expecting these environment variable to be set. _versions.py: BST_FORMAT_VERSION bumped to 18. This fixes issue #718
* NEWS: Add item for bst shell --sysroot changesJonathan Maw2018-10-301-0/+4
|
* NEWS: Add item for cached buildtree behaviourJonathan Maw2018-10-301-0/+5
|
* Added a news item for building out of the source directorywillsalmon/outOfSourecBuildWilliam Salmon2018-10-161-0/+3
| | | | For issue #512 in Gitlab.
* NEWS: Add entry about contrib/bst-docker-importChandan Singh2018-10-091-0/+3
| | | | | | | As suggested in https://gitlab.com/BuildStream/buildstream/merge_requests/857#note_106809743, add a NEWS entry for `contrib/bst-docker-import` that was added recently.
* Add NEWS entry for Source Transform and pip sourcechandan/sourcetransformChandan Singh2018-08-151-0/+7
|
* Add NEWSJonathan Maw2018-08-141-0/+4
|
* NEWS: Move recent entries to a new 1.3.1 sectionJürg Billeter2018-08-141-9/+17
| | | | | Caching failed builds and relative workspaces were not part of the 1.1.5 developer snapshot.
* Implementing relative workspacesrelative_workspacesPhillip Smyth2018-08-101-0/+4
| | | | | | | This fixes #191 A note has been added to NEWS explaining backwards compatibility issues
View Lorry Controller Status