| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Since we want the COMMITTERS list to be sync'd with the GitLab
permissions, use a script for fetching all the information and building
a table with it automatically.
The script uses a template located in the contrib/ directory.
Closes https://gitlab.com/BuildStream/buildstream/issues/1071
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the `buildstream/buildstream` image has 9 variants, let's make
it easier to choose the desired tag, using a command-line option.
This is otherwise possible by specifying the full image name `image:tag`
using the `-i` option. But, this will make it easier to specify just the
tag using `-j`.
The following two invocations of `bst-here` are now equivalent:
bst-here -i buildstream/buildstream:dev
bst-here -j dev
|
| |
|
|
|
|
|
|
|
| |
See https://gitlab.com/BuildStream/buildstream-docker-images/issues/26
for detailed discussion around this.
`buildstream/buildstream-fedora` is now considered deprecated. Switch to
`buildstream/buildstream` image. This image also offers more tags that
will provide users more flexibility.
|
| |
|
|
|
|
|
|
|
|
| |
This script leverages the recently added format strings
(`%{build-deps}`, `%{runtime-deps}`) to `bst show` to print a graph in
DOT format. This requires users to have the `graphviz` python package
installed.
Additionally, users can also render the graph using the `--format`
option if they have the `graphviz` command line tool installed.
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit marks 'bst checkout' as a 'hidden' command. If used,
the user will be prompted to use the new 'bst artifact checkout'
command.
All tests which used 'bst checkout' have been modified to use
the new artifact sub-command.
This partially solves #822.
|
| | |
|
| |
|
|
|
|
| |
In !857, we added `contrib/bst-docker-import` script but it has a small
issue that some of logs go to stdout while others go to stderr. Fix it
so that all logging is done on stderr.
|
| |
|
|
|
|
|
|
| |
This script can be useful to generate a Docker image from `bst checkout`
of an element as a single command. While this script does not eliminate
the need for a proper Docker/OCI element plugin that would probably also
support layering, it provides a cheap way to export the element into a
Docker image.
|
| |
|
|
|
|
|
|
|
| |
This method doesn't really do anything as this is already the default
behavior of `docker volume create` so remove it and always call
`docker volume create` directly. This command will always print the name
of the volume on STDOUT which is not very interesting so silence that.
(If it errors out for some reason, that output will go to STDERR so the
user should still be able to see that.)
|
| |
|
|
|
| |
As we can only accept arguments when a command is specified, make it
clear in the usage instructions.
|
| |
|
|
|
|
|
|
|
| |
One may want to mount additional volumes to preserve certain directories
or to share some data between the host and the container. Allow users to
do so by providing a `-v` option that passes its arguments to
corresponding `-v`/`--volume` option for `docker run` command.
Part of #378.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, the name of the Docker image is hardcoded in bst-here script.
This makes it harder for users to override it, which may be needed for
various reasons (custom plugins, private Docker registries etc.)
Add `-i` option to allow users to specify the base image. When `-i` is
not provided, default to `BST_HERE_IMAGE` environment variable if it's
set and otherwise to the current image -
`buildstream/buildstream-fedora`.
Also, re-order the command-line options in help text and source code in
alphabetical order to maintain sanity as the number of options is slowly
growing.
Part of #378.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
As shown in the snippet below, the `bst` binary is installed at
`/usr/local/bin/bst` in the current Docker image
`buildstream/buildstream-fedora`,
```
$ docker run --rm buildstream/buildstream-fedora type -a bst
bst is /usr/local/bin/bst
```
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If run with no arguments, `bst-here` now opens an interactive Bash
shell. This has several advantages to running each `bst` command
in a new container:
* it's faster
* bash completions will work
* man pages could work (if the user runs `dnf install man`)
If run with arguments, those are now assumed to be arguments for `bst`
such that instead of running `bst-here bst build foo` you now just run
`bst-here build foo`.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows users to distinguish bst-here shell sessions from their
regular shell.
The prompt is blue and gives you just the path name, e.g.:
/src>
The prompt can be customised or removed by editing the bst-here script
directly.
|
| |
|
