| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fixes #65
|
| |
|
|
| |
If specified, the command will run in non-interactive mode.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
`bst workspace {open,close,reset} <bst> --source <index>` commands currently
give an indexing error. The python click library needs to be told that the
expected argument is of type integer.
This patch also makes use of metavar to display a placeholder in the help
prompt, like:
-s, --source INDEX The source to create a workspace for. Projects with one
source may omit this
|
| |
|
|
|
|
|
|
|
|
| |
Remove the requirement to specify '--force' in conjunction with
'--no-checkout' if there are already files in the workspace. We won't
write anything when opening the workspace, so there's nothing to force.
For example, when opening a workspace to an existing clone of a
repository, it seems alarming to have to '--force' the workspace open.
It made me wonder if it will actually be overwritten.
|
| |
|
|
| |
Fixes #60
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Packaging is a big topic in the Python community these days. Things are
evolving, but a consensus seems to have formed around the path forward.
With PEP 518, Pip is becoming the primary tool to install Python
modules. In turn, Pip will use the right underlying tool for the job.
(distutils, setuptools, flint, ...)
Given all this, it makes sense to have a pip element in BuildStream.
This element installs a single Python module, telling Pip not to go and
download its dependencies, to make builds reproducible and not rely
on the network during builds.
By default it will use the `pip` command which generally points to Pip
for Python 2. Users can override the "pip" variable, for example to use
the `pip3` command, which generally points to Pip for Python 3.
|
| |
|
|
| |
This seems to be a simple copy-paste mistake.
|
| |
|
|
|
|
|
|
| |
To build all elements, the source bundle has to include the sources and
scripts for all elements, not just build dependencies and their runtime
dependencies.
This removes the --deps option as it doesn't make sense in this context.
|
| |
|
|
| |
Fixes #57
|
| | |
|
| |
|
|
| |
Fixes #58
|
| | |
|
| |
|
|
|
|
| |
This is equivalent to not specifying a dependency type at all.
Fixes #61
|
| | |
|
| |
|
|
|
|
|
| |
This is mainly useful for testing artifact caches and such. Most users
will hopefully be able to make use of artifact caches populated by
automated build machines, but right now it's unlikely that most people
will be pushing artifacts around.
|
| |
|
|
| |
This is required when using a push queue without build queue.
|
| | |
|
| |
|
|
| |
Strong ref was not created.
|
| |
|
|
| |
Not useful for builds, but interesting for network related tasks.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
(strict_rebuild)
This was doing a non-recursive calculation of weak cache keys, but the intention
was to do a recursive one; this is why my demo was an epic failure.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This allows plugin types to declare that their instances
must be rebuilt when their dependencies change in non-strict
build mode.
This is specifically for non-strict builds and allows appropriate
reassembly of composition elements, which take their dependencies
as verbatim input to create output.
|
| |
|
|
|
| |
The offset difference includes the padded bytes of the last file, i.e.,
up to 511 bytes in addition to the 512 byte block.
|
| | |
|
| |
|
|
|
| |
Now includes man pages for workspace commands and
also the bst-artifact-receive helper program.
|
| | |
|
| |
|
|
|
| |
Ensure all objects have been sent before moving them into the repository
and do not terminate pusher while receiver is still processing.
|
| |
|
|
|
|
|
| |
dpkg_build artifacts used to include a DEBIAN/ dir containing a bunch
of files which didn't even come from the same package.
This commit removes them, to avoid future confusion.
|
| |
|
|
|
| |
When writing the yaml, pre-install and post-install scripts' fields are
named "preinst" and "postinst", not "preinstall" and "postinstall"
|
| |
|
|
|
|
| |
Retry network tasks up to two times by default.
Fixes #30
|
| |
|
|
|
| |
Move parent_start_listening() from __init__ to spawn() to support
respawning a job after shutdown.
|
| | |
|
| |
|
|
|
|
| |
Unexpected connection termination should not be considered a bug.
Fixes #51
|
| |
|
|
|
| |
If --on-error is specified to decide the failure action on the command line,
then dont interactively handle that decision.
|
| |
|
|
|
| |
Before we were assuming the user would specify a cwd which exists,
now we dont care and just create it if it's not there.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The pusher already checks this and the check in the receiver does not
provide any additional guarantees as it is prone to race conditions.
This prevents a push error in case two clients push an artifact with the
same key around the same time.
Fixes #52
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the main BuildStream process the foreground process again when the
interactive child exits. Otherwise the next read() on stdin will trigger
SIGTTIN and stop the process. This is required because the sandboxed
process does not have permission to do this on its own (running in
separate PID namespace).
dash still prints an error because it fails to restore the foreground
process, however, this is harmless. bash doesn't print an error in this
case, but the behavior is otherwise identical.
Fixes #41
|
| |
|
|
| |
Fixes #49
|
| |
|
|
|
| |
Add an extra argument to the function to know which elements
were already resolved.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the first time you configured an artifact cache, you would
get to the end of your first build and then BuildStream would exit
because of some stupid mistake like you got the address slightly wrong
or you forgot to add the host keys of the remote artifact cache to
`~/.ssh/known_hosts`.
To avoid surprises, if there's an artifacts push-url configured we now
try to connect to it as a preflight check so that issues are raised
early.
On success, you will see something like this:
[--:--:--][90904fe4][ main:gnu-toolchain/stage2.bst ] START Checking connectivity to remote artifact cache
[00:00:00][90904fe4][ main:gnu-toolchain/stage2.bst ] SUCCESS Connectivity OK
On failure, it looks like this:
[--:--:--][90904fe4][ main:gnu-toolchain/stage2.bst ] START Checking connectivity to remote artifact cache
[00:00:03][90904fe4][ main:gnu-toolchain/stage2.bst ] FAILURE BuildStream will be unable to push artifacts to the shared cache: ssh: connect to host ostree.baserock.org port 2220: Connection timed out
As a bonus, for some reason this check causes SSH to ask about unknown
host keys rather than just failing, so you may now see messages like
this if the host keys are unknown rather than an error:
The authenticity of host '[ostree.baserock.org]:22200 ([185.43.218.170]:22200)' can't be established.
ECDSA key fingerprint is SHA256:mB+MNfYREOdRfp2FG6dceOlguE/Skd4QwnS0tvCPcnI.
ECDSA key fingerprint is MD5:8f:fa:ab:90:19:31:f9:f7:f1:d4:e5:f0:a2:be:56:71.
Are you sure you want to continue connecting (yes/no)?
|
| |
|
|
|
|
|
| |
The full ref list can easily exceed the maximum message size. Limit list
to refs being pushed.
Fixes #47
|
| |
|
|
|
| |
If push-url is specified, it must point to the same repository as
pull-url as the summary file is used for pull and push operations.
|
