| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
Workspace changes are now detectable when using BuildBox as the sandbox
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`track` and `fetch` become noop methods and the workspace is imported
into the CAS in the call to `get_unique_key` which also sets the digest
attribute and owns that Directory object. The directory is referenced
during stage to import directly to the virtual directory object.
Importing is expected to be expensive and will be
optimised in future.
When the unique key is retrieved for the workspace source it will also
be commited to the sourcecache. The logic for this source is still a
slight variant on other sources since it cannot itself be expected to
be in the cache when it's opened.
|
| | |
|
| |
|
|
|
| |
Opening and building workspaces when buildbox is the sandbox is now
supported.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Check that sources are cached even if they are workspaced.
|
| | |
|
| |
|
|
|
|
|
|
| |
Using the workspace source plugin, workspaces should now be handled like
sources for the purpose of calculating element cache keys.
partially reverts !1470
works towards #1073
|
| |
|
|
|
| |
partially reverts !1470
closes #1088
|
| |
|
|
|
|
| |
The `workspace.init_workspace()` call should wrap
`source._init_workspace` for held sources to support those sources not
publishing `BST_VIRTUAL_DIRECTORY`
|
| |
|
|
|
| |
If the source is a workspace source, the fullpath of the project_dir
should be preserved in loading source local paths.
|
| |
|
|
|
| |
Add the workspace-kind source to the sources manually to prevent a user
incorrectly loading the source plugin.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
pytest-cov 2.7 calls os._exit() in its SIGTERM handler, skipping
cleanup, unless another SIGTERM handler was already registered.
Add our own SIGTERM handler to the subprocess to ensure proper cleanup
such as terminating buildbox-casd.
|
| |
|
|
|
|
| |
Now that the frontend has been mostly reworked/standardized,
this patch attempts to put our some guidelines/information in
around UI contributions.
|
| |
|
|
|
| |
This patch adds internal cross references for the artifact and
source commands.
|
| |
|
|
|
| |
This patch ensures that we document the recently introduced
artifact subcommands "show" and "list-contents".
|
| |
|
|
|
| |
Adds an integration test to check the `pass-integration` option for
filter elements works.
|
| |
|
|
|
|
|
|
| |
Currently the stack element does not produce an artifact, and sometimes
has to be treated differently because of this. It is conceivable that
someone will write a plugin that must be treated similarly and doesn't
produce an artifact. As a result this commit abstracts this "not
producing an artifact" feature of elements.
|
| |
|
|
|
|
|
|
|
|
|
| |
As stack elements do not provide any artifacts, it is misleading to
allow them as dependencies for filter elements. This commit makes a
dependency on a stack element a failure with a descriptive error
message.
Additionally adds a test to make sure this works.
Addresses #1104
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It is tedious to manually copy the integration commands of the parent
element into a filter element, so this allows it to be done
automatically. Here we modify FilterElement.integrate() to allow us to
pass through the parent's integration commands, iff an option is set.
Also adds a test for the new feature, but this is not as comprehensive
as would be idea, as getting to the integration commands which are run
is a little more difficult.
Addresses #1107
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Our contributing has got way too big. This patch aims to
split it up into sensible files. These are found in
"Further information".
Closes #1116
|
| |
|
|
|
|
|
| |
This patch ensures checkout behaves like the rest of our
commands which support --deps options. That is, we carry
the "deps" string through to the Stream and load the
corresponding PipelineSelection.
|
| |
|
|
|
|
|
|
| |
source checkout supports --deps all, so we should be
consistent.
Additionally, a user may want to have build deps in a
potential chroot so you could rebuild any component.
|
| |
|
|
|
| |
Since the majority of the NEWS entries seem to be written in the past
tense, change the handful of entries that aren't.
|
| |
|
|
|
|
|
|
| |
This was incorrectly copy-pasted in the wrong location.
See
https://gitlab.com/BuildStream/buildstream/commit/108a38edd86d9de3ef0ce78cb005041662ed279e#note_216141606
for related discussion.
|
| |
|
|
|
|
| |
The current mentions of `source checkout` in the NEWS file
have been updated so that they explain the recent changes to
`bst source checkout`
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
!1451 introduced the --compression option to bst artifact checkout.
This MR is a step towards making the commands more symmetric,
and introduces the --compression option to bst source checkout
Now we're compressing, we must explicitly close the tarball
once we're done writing to it.
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch introduces a local _handle_compression() function,
which returns a string representing the "mode" of tarfile
compression required by the TarFile object.
In addition to this, _export_artifact() has been changed
so that it now uses this new function
See: https://docs.python.org/3/library/tarfile.html#tarfile.open
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This MR changes the behaviour of source checkout so that it is more
like artifact checkout. That is, a --directory option can be provided,
rather than a mandatory LOCATION.
In addition to this, the --tar option is no longer a boolean flag,
rather it expects a tarfile name (just like artifact checkout)
The appropriate tests have also been altered so that they support
the new API
|
| | |
|
| |
|
|
|
| |
_export_artifact() is not a trivial function and thus
deserves a doc comment
|
| |
|
|
|
|
| |
In "test_source_checkout_force()" we had a commented out line
of code. This has been removed and a more useful comment has been
added.
|
| | |
|
| | |
|
| |
|
|
|
| |
bst-1.x support BST_FORMAT_VERSION == 17, as that is not supported by
master I think is ok to set BST_FORMAT_VERSION_MIN = 18
|
