| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This will not fix the CI but at least we can see what is the actual
error when trying to build (Rigth now It doesn't build at all
because the format version is not compatible)
|
|\
| |
| |
| |
| | |
Report when Buildbox-casd is not alive at the end of a run
See merge request BuildStream/buildstream!1605
|
| |
| |
| |
| |
| |
| |
| | |
This adds messages in the various mis-termination of Buildbox-casd, to
notify users that something might have gone wrong there.
It also adds a few tests to validate the various behaviors.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Do not check for casd in bash completion
Closes #1149
See merge request BuildStream/buildstream!1615
|
|/
|
|
|
|
|
|
|
| |
This caused stacktraces when a user didn't have buildbox-casd
installed, even though it wasn't required for completion, even for
artifacts.
It does add a slightly ugly parameter to Context, long-term it might
make sense to create a special slimmed-down context for completion.
|
|\
| |
| |
| |
| |
| |
| | |
Use buildbox-casd CaptureTree() to import directories
Closes #1132
See merge request BuildStream/buildstream!1611
|
| | |
|
| |
| |
| |
| |
| | |
This allows import of a whole directory tree with a single gRPC call to
buildbox-casd CaptureTree() instead of importing files one at a time.
|
|/ |
|
|\
| |
| |
| |
| | |
NEWS: Minor fixups
See merge request BuildStream/buildstream!1614
|
| |
| |
| |
| | |
Add a placeholder section to hold newsworthy items for the next release.
|
|/
|
|
|
| |
Since we decided to release the snapshot version '1.91.0', this patch
updates the version information in the NEWS entry accordingly.
|
|\
| |
| |
| |
| | |
_context.py: Remove duplicated log_message_lines assign
See merge request BuildStream/buildstream!1610
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
workspaces via sourcecache 1
Closes #1088
See merge request BuildStream/buildstream!1563
|
| |
| |
| |
| | |
Workspace changes are now detectable when using BuildBox as the sandbox
|
| |
| |
| |
| |
| | |
Opening and building workspaces when buildbox is the sandbox is now
supported.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Workspaces will be handled via the workspace source plugin methods. This
does not currently support reflecting build artifacts in the open
workspace.
tests: Mark incremental workspace builds as xfail (strict)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Check that sources are cached even if they are workspaced and do not
reset workspace cache data
partially reverts !1470
closes #1088
element.py: remove workspaces in cache key calc
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
Since the source keys are now calculated using the unique keys of the
workspace source, this change will break external tracking for open
workspaces. In future attempting to track an open workspace might raise
a SourceError. The test is rewritten to close the workspace before
tracking.
|
| |
| |
| |
| |
| | |
Add the workspace-kind source to the sources manually to prevent a user
incorrectly loading the source plugin.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `workspace.init_workspace()` call should wrap
`source._init_workspace` for held sources to support those sources not
publishing `BST_VIRTUAL_DIRECTORY`
This object owns a directory digest attribute used inplace of the source
ref.
`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.
In the source preflight method the preflights of the held sources must
be called.
|
|/ |
|
|\
| |
| |
| |
| | |
tests: Add some missing integration marks
See merge request BuildStream/buildstream!1609
|
|/ |
|
|\
| |
| |
| |
| | |
Do not directly communicate with CAS server
See merge request BuildStream/buildstream!1601
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
All communication with CAS servers should be proxied through
buildbox-casd to allow connection sharing among job subprocesses.
It is no longer needed to query the server capabilities as buildbox-casd
already does that, so we can simply remove the code from BuildStream.
|
| |
| |
| |
| | |
Remote CAS servers should not be contacted directly.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The push status check is implemented by BuildStream artifact and source
services. It's not part of the CAS protocol.
|
| |
| |
| |
| |
| |
| |
| | |
It's sufficient to check the capabilities once per bst session. This
avoids the extra round trip in remote.init().
This also adds a check for allow_updates for push remotes.
|
| |
| |
| |
| |
| |
| |
| | |
It's sufficient to check the capabilities once per bst session. This
avoids the extra round trip in remote.init().
This also adds a check for allow_updates for push remotes.
|
|/
|
|
|
| |
There is no need to create a new stub for every request. This also
matches what SourceRemote does.
|
|\
| |
| |
| |
| | |
tests/testutils/artifactshare.py: Add SIGTERM handler to subprocess
See merge request BuildStream/buildstream!1606
|
|/
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
Add UI section in CONTRIBUTING
See merge request BuildStream/buildstream!1584
|
| |
| |
| |
| |
| |
| | |
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".
|
|\
| |
| |
| |
| |
| |
| | |
plugins/elements/filter.py: Allow passing integration commands through, fail if dep is a stack element
Closes #1107 and #1104
See merge request BuildStream/buildstream!1593
|
| |
| |
| |
| |
| | |
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
|
|\
| |
| |
| |
| |
| |
| | |
Split up CONTRIBUTING
Closes #1116
See merge request BuildStream/buildstream!1604
|