| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| | |
This doesnt match exactly the same way it happened in master,
so fixing it up in a separate commit.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will allow cross-junction dependencies to be listed as strings on a
single line.
As part of this, some logic around initializing `Dependency()` objects
have been moved out of `_extract_depends_from_node()` method into the
constructor of `Dependency()` class, to keep all related code in one
place.
* _loader/types.py: While initializing `Dependency` objects, attempt to
split filenames, only if no `junction` was specified
explicitly. If a `junction` was specified, then
filenames with `:` in their names will result in an
error.
* _loader/loadelement.py: Refactor logic to initialize `Dependency()`
objects to move it to the `Dependency()`
constructor.
* tests/frontend/buildcheckout.py: Add tests to ensure the above.
* _versions.py: Bump BST_FORMAT_VERSION.
Fixes #809.
|
|\
| |
| |
| |
| | |
Backport build/runtime depends shorthand
See merge request BuildStream/buildstream!1501
|
| | |
|
| | |
|
| |
| |
| |
| | |
Format version raised because of a change to the core element format.
|
| | |
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Backport ability to see previous sources in fetch() and track()
See merge request BuildStream/buildstream!1477
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Updates the refs in the job process (but doesn't write), to ensure
following sources can see consistency of previous sourcse has been
updated. `_save_ref` is renamed `_set_ref` with writing to file now
optional.
This also changes the previous_source_access test to use a remote, so
that it actually tests this cornercase.
Fixes #1010
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`pip` source plugin can stage python packages that are either specified
directly in the element definition or picked up from `requirements.txt`
from previous sources. In order to support the latter use-case
(which is also the primary motivation for this plugin), this plugin
requires access to previous sources and hence is an example of a
Source Transform source.
Also, bump `BST_FORMAT_VERSION` as this patch adds a new core plugin.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Source plugin implementations can now specify that they need access to
previously staged sources by specifying
`BST_REQUIRES_PREVIOUS_SOURCES_TRACK` and/or
`BST_REQUIRES_PREVIOUS_SOURCES_FETCH`, corresponding to access at `track`
and `fetch` times respectively.
Fixes #381.
Replaces !505. For relevant discussion, see this discussion:
https://gitlab.com/BuildStream/buildstream/merge_requests/505#note_83780747
|
|/
|
|
|
|
|
| |
Since we may have python files in there which are not expected
to be loadable directly in the test environment (they are project data),
we should not have the tests automatically recurse into there and
assume it can collect tests from there.
|
|\
| |
| |
| |
| | |
Add max-jobs configuration and command line option (bst 1)
See merge request BuildStream/buildstream!1474
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This tests that the resolution of the `max-jobs` automatic variable
is properly controlled by the new user configuration and command
line option, including the default automatic '0' value.
Regression test for #1033
|
| |
| |
| |
| |
| |
| |
| | |
Only use automatic max-jobs by default if the user has not
requested a specific value for max-jobs.
This is a part of #1033
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While this is currently only relevant for `bst build`, it is
a current implementation detail that user configuration which
gets overridden by command line options must use toplevel
options.
This patch allows invocations such as the following to override
the max-jobs:
bst --max-jobs 16 build target.bst
This also updates the completions test to expect the new toplevel option.
This is a part of #1033
|
|/
|
|
|
|
|
|
| |
This loads the configuration of the max-jobs variable
from the user configuration, where the default is 0
(meaning use the maximum number of cores with a limit of 8).
This is a part of #1033
|
|\
| |
| |
| |
| | |
_frontend/cli.py: Exit with error if output streams are set to nonblocking
See merge request BuildStream/buildstream!1389
|
|/
|
|
|
|
|
| |
This is better than raising a stack trace later on when logging gets
intense with a BlockingIOError.
This fixes #929
|
|\
| |
| |
| |
| | |
tests/artifactcache/expiry.py: Disable test failing on builders
See merge request BuildStream/buildstream!1436
|
|/ |
|
|\
| |
| |
| |
| | |
Fix workspaced junctions (1.2)
See merge request BuildStream/buildstream!1355
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
junctions
We already test the behavior without workspaces, lets just augment
these tests to also run with a workspaced junction and check the results.
This guards against regressions of #1030.
|
|/
|
|
|
|
|
|
|
|
| |
Instead of looping over the sources directly, we should be using
the canonical way of checking element consistency.
This requires an additional call to Element._update_state() on the
freshly loaded junction element in order to ensure we calculate consistency.
This fixes issue #1030.
|
| |
|
|\
| |
| |
| |
| | |
Backport !792 to bst-1.2
See merge request BuildStream/buildstream!1338
|
| | |
|
|/
|
|
|
|
|
|
| |
bst build returns "missing project.conf" when a project.conf is invalid
This results in an existing project with malformed yaml being dismissed
and attempts to make a new project
Added new exception
|
|\
| |
| |
| |
| | |
Fix build track all no strict 1.2
See merge request BuildStream/buildstream!1331
|
| |
| |
| |
| |
| |
| | |
actually build
This is a regression test for issue #1014
|
| |
| |
| |
| |
| | |
This adds a check to test_build_track() to ensure that the target
is cached as a result of building with tracking of selected elements.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When calculating the strict key, we do not know for sure yet that the
element is required or whether it will ever have a cache key, as
we could be tracking elements which will result in resolving an
element which is a build-only dependency of the target.
This ensures that we process all elements which need to be processed,
which is important for cases where we are building in non-strict mode
and tracking is also enabled.
This fixes issue #1014
|
|\
| |
| |
| |
| | |
element.py: Reset workspace state if last successful build is missing (1.2)
See merge request BuildStream/buildstream!1329
|
| |
| |
| |
| |
| |
| | |
artifacts are deleted
This is a regression test for #1017
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
subdirs.
The artifact directories are based on the element normal_name, which
substitutes any path separators with dashes.
Fix the helper function to use the correct path.
|
|/
|
|
|
|
|
|
| |
If the artifact referred to by the last successful build in the
workspace state no longer exists, reset the workspace state and
do not attempt to perform an incremental build instead of crashing.
This fixes #1017
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Add fedora 30 to coverage report
See merge request BuildStream/buildstream!1326
|
|/ |
|
|\
| |
| |
| |
| | |
_artifactcache.py: display the actual key being pulled
See merge request BuildStream/buildstream!1305
|
|/
|
|
| |
Fixes #981
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Remove deprecated F28
See merge request BuildStream/buildstream!1321
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Tristan/fix cloned plugin ids 1.2
See merge request BuildStream/buildstream!1315
|
| |
| |
| |
| |
| |
| | |
When cloning a Source, we should inherit the same unique ID for
the sake of sending a valid ID in any messages sent back to
the frontend from a source cloned in a child task.
|