| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This seems to be debug print left around in the branch.
|
|
|
|
|
| |
The information provided by link_files is not sufficient to know which
element had the overlapped file.
|
|
|
|
|
|
|
|
| |
o Use the * parameter to denote keyword-only arguments
o Remove the docs mentioning that it is specifically for the
compose element use case, while it's only used here currently,
it is not necessarily true.
|
|
|
|
| |
Fixes issue #147
|
|
|
|
|
|
|
| |
Now that recurse is a mandatory keyword argument, the docs
should also reflect this; this must be done manually because
we override the signature here in the docstring, to hide some
private arguments.
|
| |
|
|
|
|
|
| |
It is functionally similar to dict.get() and fulfills the same role, so
it should be used that way.
|
|
|
|
|
| |
Since the 'recurse' arg is a boolean, using it as an argument without a
keyword is likely to cause confusion.
|
|
|
|
|
| |
The arguments are optional, and none of the arguments depend on each
other, meaning that they do not make sense as optional positional arguments.
|
|
|
|
|
|
|
| |
When reading element.py, I was surprised that it was importing
'inspect'.
Remove that import and some other unused ones to improve readability.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Consequently:
o Changed Plugin.get_context() to a private Plugin._get_context() accessor.
o Updated anything which imports Context to do so from private _context module
o Updated docs to exclude the now private Context
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This required adding two new APIs to make up for it on the Source
o get_project_directory()
Added here because elements should not be accessing external
resources, Sources needed for local files and GPG keys and such
o translate_url()
Used by sources to mish-mash the project aliases and create
real urls.
|
|
|
|
|
|
| |
Base class for exceptions is now a part of the already private _exceptions module
Also moved PipelineError from _pipeline -> _exceptions module
|
|
|
|
| |
This is now part of the already private _exceptions module
|
|
|
|
| |
Hide all of buildstream's internal exceptions from the API surface.
|
|
|
|
|
|
|
|
|
|
| |
create SandboxError
These errors are a part of public facing API, and the exceptions
module contains a lot of internal details to be hidden from public API.
This move required creating SandboxError because sandbox related
code had previously been hijacking the ElementError and raising that.
|
| |
|
| |
|
|
|
|
|
| |
This is the correct place for the check, once for each element in
the overall source staging directory.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Part of issue #81
This was failing because the tmpdir contextmanager was trying to still
use it's own mechanics to cleanup the artifact assembly directory.
This is fixed by *not* using a tmpdir, which was just wrong to begin
with because we're already working inside a temp directory.
|
|
|
|
|
|
| |
This is there because an ArtifactError on failure to commit indicates
some permissions issue with the directory structure, and it's better
to not leave this dangling behind for users to deal with.
|
| |
|
|
|
|
|
| |
This was used to show which variants had been selected when
printing out the pipeline.
|
|
|
|
|
| |
Consequently improved _yaml.node_sanitize() to omit a crazy lambda
which had no effect at all on the outcome of the function.
|
| |
|
| |
|
|
|
|
|
|
| |
o The command argument is a list, not a string
o The default value for the command list is ['sh', '-i']
o The sandbox is always run interactively
|
| |
|
| |
|
|
|
|
|
|
| |
Instead use BST_STRICT_REBUILD and follow a new pattern we're
using for any class attributes used for the plugin to communicate
static data back to the core.
|
|
|
|
|
|
|
|
|
|
|
| |
Starting to go with using class attributes in some
cases for the plugin to communicate static things
like required version and strict rebuild policies.
This is interesting because class attributes suggest
that you cannot return something dynamic, and at the
same time class attributes are useful at times when
you have a plugin type but no instance.
|
|
|
|
|
|
|
|
|
| |
Instead of just being able to specify what domains to include and
whether to include orphans, also specify what domains to exclude.
This allows one to deal with situations with overlapping rules
more dynamically; i.e. one can include all of `/usr/bin/*` and
then specifically exclude `/usr/bin/gcc` by itself.
|
|
|
|
| |
If specified, the command will run in non-interactive mode.
|
|
|
|
| |
This is required when using a push queue without build queue.
|
|
|
|
|
|
|
| |
(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.
|
| |
|
|
|
|
| |
Fixes #49
|
| |
|
|
|
|
| |
They are no longer needed.
|
| |
|
|
|
|
|
| |
Build planning uses list of artifacts in remote artifact cache. Pull
failures cannot be ignored.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reflects the selected variant at load time, otherwise None for
elements which do not declare any variants.
|