| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Update bst-plugins-experimental version to 1.93.1.1
See merge request BuildStream/buildstream!1815
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Prepare 1.93.1 development snapshot
See merge request BuildStream/buildstream!1814
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
_sandboxbuildboxrun.py: Support host-files
See merge request BuildStream/buildstream!1807
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
This breaks if host-files is used to bind mount regular files.
|
| |\
| |
| |
| |
| | |
tests/integration/interactive_build.py: Relax expect for buildbox-run
See merge request BuildStream/buildstream!1801
|
| |/
|
|
|
| |
When commands are batched, the failure message can't include the command
group label with buildbox-run.
|
| |\
| |
| |
| |
| | |
.gitlab-ci.yml: Update BuildBox components to 0.0.6
See merge request BuildStream/buildstream!1813
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
.gitlab-ci.yml: build fdsdk needs cargo plugin and its dependencies
Closes #1259
See merge request BuildStream/buildstream!1812
|
| |/ |
|
| |\
| |
| |
| |
| | |
.gitlab-ci.yml: Bump bst-plugins-experimental
See merge request BuildStream/buildstream!1811
|
| |/
|
|
|
|
|
|
|
|
|
| |
When we updated the entrypoints for the plugins, the
bst-plugins-experimental version used for overnight tests was not
bumped, which means that the plugins used in freedesktop-sdk don't get
detected.
This commit bumps this to the latest snapshot of
bst-plugins-experimental, and downloads directly from PyPI rather than
installing from git.
|
| |\
| |
| |
| |
| | |
Improvements to _GitSourceBase and _GitMirror
See merge request BuildStream/buildstream!1808
|
| | | |
|
| | |
| |
| |
| |
| | |
This includes adding an entry for the recursive submodules changes from !1765,
and adding myself to the authors of _gitsourcebase.py.
|
| | |
| |
| |
| |
| | |
The functionality has been split into three new functions:
to_commit, reachable_tags, and describe. No behaviour is changed.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The beginning parts of git-describe labels are completely arbitrary.
They can be changed either manually or by a track (e.g. if a tag is
moved, added or deleted) even if the referenced commit is the same.
Hence, only the commit ID part of the label should factor into the cache
key.
This commit, of course, breaks cache keys for artifacts built with the
'git' source with git-describe refs.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
This changes how the Git repo in the source cache is managed.
The mirror is not created with an initial clone, but is set up manually from
an empty repo. This is to support shallow cloning in future changes.
To simplifiy code and Git calls, remotes are no longer used; instead URLs
are passed on the command-line.
|
| |\
| |
| |
| |
| |
| |
| | |
Stop plugin tests using private API
Closes #1258
See merge request BuildStream/buildstream!1806
|
| | |
| |
| |
| |
| |
| |
| | |
Adds functions to the `buildstream.testing` package to allow plugins to
dump elements and projects on the fly. Before this plugins were just
accessing the private yaml API for tests and loading/dumping directly. I
also allow access to just `_yaml.load()` from testing.
|
| |/
|
|
|
|
|
| |
Plugin tests are already accessing this API, but using imports from
private modules. For motivation for this to be exposed publicly, note
that ErrorDomain is an argument for most things in runcli.py, and
LoadErrorReason may be another.
|
| |\
| |
| |
| |
| |
| |
| | |
_frontend/cli.py: Make show() --use-buildtree respect pull semantics
Closes #1151
See merge request BuildStream/buildstream!1767
|
| |/
|
|
|
|
|
| |
Ensure that if a buildtree isn't cached locally, it's only fetched
if --pull and pull-buildtrees config are set. Also, only attempt to
fetch if it's plausible that it could be pulled, with appropriate
messaging based on local cached state.
|
| |\
| |
| |
| |
| | |
element.py: Optimize assemble_done()
See merge request BuildStream/buildstream!1802
|
| |/
|
|
|
| |
After a successful build we know that the artifact is cached. Avoid
querying buildbox-casd and the filesystem.
|
| |\
| |
| |
| |
| | |
NEWS: Add mark for 1.93.0
See merge request BuildStream/buildstream!1804
|
| |/
|
|
| |
Prepare for next release.
|
| |\
| |
| |
| |
| | |
Plugins: Update entrypoint group for pip origin
See merge request BuildStream/buildstream!1803
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Update sample plugin documentation based on the recent change to entry
point group for plugins.
While I'm here, also remove the unnecessary dependency on `setuptools`
from the sample plugin.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed in
https://mail.gnome.org/archives/buildstream-list/2020-January/msg00001.html,
separate the entry point groups for elements and sources. Previously,
both used `buildstream.plugins` which meant that it wasn't possible to
have an element and a source plugin with the same name, when using `pip`
origin.
This a breaking change for all plugins, but will only affect projects
using the `pip` plugin origin.
As part of this, also bump the version of bst-plugins-experimental used
in our tests to avoid CI breakages.
|
| |\
| |
| |
| |
| | |
Remove deb surce plugin, it has beem moved to bst-plugins-experimental
See merge request BuildStream/buildstream!1729
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Optimize consistency and state handling
Closes #1126
See merge request BuildStream/buildstream!1739
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This assert would only be run in development mode and would actually not
mark the source as downloaded. Therefore forcefully mark them as fetched
and remove the assert. Our test suite will catch if there is a problem.
|
| | |
| |
| |
| |
| | |
'Consistency' is not needed anymore, now that we have everything in
place to not use it
|
| | |
| |
| |
| |
| | |
By looking at the flag first, we can avoid expensive checks on whether
the element is cached or not.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the early call to get whether sources are locally cached
in `_update_source_state` by delegating it to the call of `is_cached`.
Once it is cached, the element is assumed to stay that way for the
duration of the pipeline, we can therefore cache the result once it is
true.
Also remove `Consistency.IS_CACHED`, which is not used anywhere else.
|
| | |
| |
| |
| |
| | |
This is not needed now that we have 'is_resolved' and 'is_cached'.
We can therefore drop all calling places and implementations of it.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the need to use consistency in Sources, by asking
explicitely whether the source is cached or not.
This introduces a new public method on source: `is_cached` that needs
implementation and that should return whether the source has a local
copy or not.
- On fetch, also reset whether the source was cached or set if as
cached when we know it was.
- Validate the cache's source after fetching it
This doesn't need to be run in the scheduler's process and can be
offloaded to the child, which will allow better multiprocessing
|
