| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
Seems that the "commands" is taking a lot of space such that
we can't see the other sections here easily, that is alright
if "commands" remains at the end.
|
| |
|
|
|
| |
Here we're really listing examples, a ToC with depth is
not great here.
|
| |
|
|
| |
project on gitlab.
|
| |
|
|
| |
This was named autotools-flatpak, changed to flatpak-autotools.
|
| |
|
|
|
| |
We still have a few unused artifacts in the docs generation,
this is just one less.
|
| |
|
|
|
|
| |
This branch fixes #312 by using a hidden toctree to include
the buildstream package and reducing the amount of allowed :orphan:
pages.
|
| | |
|
| | |
|
| |
|
|
|
| |
This is nice to have on the main page, and is only a few links, dont
like having a whole toplevel ToC entry for this.
|
| | |
|
| |
|
|
|
| |
Sphinx generates some library style module index, we just include
it in a hidden toctree and avoid using it altogether.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
o Now the page titles are declared in plugins, allowing for
a more descriptive ToC
o Makefile and plugin.rsttemplate updated to not produce the title,
to no longer use `:orphan:` for plugin pages, and to ignore any
private modules in the plugin directories.
o Interestingly, now the docs will fail to build if you add
a new plugin and forget to add it to the documentation.
|
| |
|
|
|
| |
The main page has too much information on it otherwise, we want
a friendly, not overwhelming first page to our docs.
|
| |
|
|
|
|
|
| |
--track-cross-junctions now concerns crossing junctions rather than
forbidding elements in sub-project to be tracked.
Part of #359.
|
| |
|
|
|
|
|
|
|
|
|
| |
Workspaces are now index by colon separated junction path. This
now allows to create workspaces for elements in external projects.
Workspaces are owned by context instead of root project. However
it is initialized once top-level project is registered as we need
to resolve paths relatively to this top-level project.
Part of #359.
|
| |
|
|
|
| |
Make it clear we expect the top-level project here as we use it to
resolve paths relative to project directory.
|
| |
|
|
|
|
| |
'a.bst:b.bst' gets interpreted as 'b.bst' from junction 'a.bst'.
Part of #359.
|
| |
|
|
| |
This closes #256
|
| |
|
|
|
|
|
| |
oversized artifacts
This user facing string was redundantly declared in two places, only
the message when catching the error was ever printed.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The tests include a new environment variable: BST_CACHE_QUOTA.
This variable is used in receive_main() in pushreceive.py.
Test names: test_artifact_expires, test_large_artifact_is_not_cached_remotely
test_recently_pulled_artifact_does_not_expire: marked as xfail until
we implement LRU expiry in remote share
|
| |
|
|
|
|
| |
New file consisting of functions that allow us to generate elements
on the fly
__init__.py now includes create_element_size()
|
| |
|
|
| |
This fixes #136
|
| | |
|
| |
|
|
|
| |
The unused list_remote_refs() function has also been removed as
part of this commit.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
o This supports deeply nested commands as well as shallow commands
o Automated support for bash completions included
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
subdirectory
The previous commit added support for running bst commands form
subdirectories of the project root. Make autocomplete also work in a
similar way.
|
| |
|
|
|
|
|
|
| |
When initializing the project, BuildStream will continue searching for
project.conf in parent directories in case it is not found in the
current directory.
Fixes #368.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It can be confusing, especially to new BuildStream users, that the CLI
expects targets to be specified relative to element-path and not the
current directory. Previously, the CLI would give a generic message
stating that the file could not be found but it was not obvious that it
was looking in the `element-path` directory.
Explicitly print the element-path in the summary. Also, try to check if
the specified element exists in the elements directory and print a hint
to use the element-path relative paths if that's the case.
Fixes #396.
This is is also related to #341. This commit aims to tackle that issue
by trying to educate users about element-path.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
For addition of new `make` plugin
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CLI for `bst-artifact-receive` expects a `repo` argument, which is
supposed to be a directory, but Click currently expects it to be just
any string. This results in stack traces like the one below when the
argument provided is not a directory:
$ ~/.local/bin/bst-artifact-receive --pull-url http://foo foobaz
Traceback (most recent call last):
File "/root/.local/bin/bst-artifact-receive", line 8, in <module>
sys.exit(receive_main())
...
File "/src/buildstream/buildstream/_artifactcache/pushreceive.py", line 581, in __init__
self.repo.open(None)
GLib.Error: g-io-error-quark: /src/buildstream/43fref: opendir(/src/buildstream/foobaz): No such file or directory (1)
Add types for this argument such that it throws better error messages
when it receives bad arguments. With the Click types added, it will
instead fail with messages like these:
$ ~/.local/bin/bst-artifact-receive --pull-url http://foo foobaz
Usage: bst-artifact-receive [OPTIONS] REPO
Error: Invalid value for "repo": Directory "foobaz" does not exist.
$ ~/.local/bin/bst-artifact-receive --pull-url http://foo setup.py
Usage: bst-artifact-receive [OPTIONS] REPO
Error: Invalid value for "repo": Directory "setup.py" is a file.
Fixes #409.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The cleanup was supposed not to remove folders (`/dev`, `/tmp`, `/proc`) if
they already existed before bwrap but it did the opposite: it tried to remove
them if they existed before, and didn't remove them if they were created during
bwrap. This was caused by a `not` clause, and this removes it.
Fixes #379
|
| |
|
|
|
|
| |
This adds `sandbox-bwrap/test-cleanup.bst` to test the cleanup behaviour in
`sandbox/_sandboxbwrap.py`: There already exists a non-empty `/tmp` folder and
BuildStream should not try to remove it after a command is executed with bwrap.
|
| | |
|
| | |
|
