| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to depend on a project which is in a subdirectory
of a Git repository.
The error message given when the expected project.conf file is not found
has also been improved. Previously the error would look like this:
Error loading pipeline: Could not find file at
/home/sam/.cache/buildstream/build/freedesktop-sdk-junction-rvmn17s2/project.conf
This is giving the path of an internal temporary directory where the foreign
project's source is checked out. The new error gives more information:
Error loading pipeline: Could not find the project.conf file for junction
element at freedesktop-sdk-junction.bst [line 1 column 0]. Expecting a
project at path '.' within git source at freedesktop-sdk-junction.bst [line
4 column 2]
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This introduces junctions as a new kind of elements to allow
dependencies to cross project boundaries.
|
| |
|
|
| |
Loader access will be required for junctions.
|
| |
|
|
| |
With junctions, elements may be loaded from multiple projects.
|
| |
|
|
| |
Project access will be required for junctions.
|
| |
|
|
| |
Element and source factories use a project-specific search path.
|
| |
|
|
| |
cli_options are project-specific.
|
| | |
|
| |
|
|
|
| |
This ensures that overlap warnings from projects without
fail-on-overlaps are not reported in fatal error messages.
|
| |
|
|
| |
It has already been migrated.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This test covers #225.
|
| |
|
|
|
|
|
|
| |
This fixes `bst shell` crashes in the presence of overlaps.
Fixes #225
Fixes: 2aa233da ("element: Handle overlaps with a whitelist and...")
|
| | |
|
| |
|
|
|
| |
Now that we consider the arch and os for every artifact, lets
bump the core artifact version to make this trackable.
|
| |
|
|
|
|
| |
Do this by default for every element, later we will have
to handle it differently when supporting projects which
build on specific arches with virtualization or networked workers.
|
| | |
|
| |
|
|
|
|
| |
This was pushed accidentally.
This reverts commit 34a60189be63dc86d333ca895ce44bd24adb43c3.
|
| | |
|
| |
|
|
|
|
|
|
| |
SafeHardlinks FUSE needs to hold file descriptors for all processes in
the sandbox. Avoid hitting the limit too quickly by increasing the soft
limit to the maximum.
Fixes #232
|
| |
|
|
|
|
| |
jinja2 2.10 import time has been divided by two compared to Jinja 2.9.6
Fixes #194
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The key change is to document the correct usage of the conf-local
and conf-global style options, as it was previously impossible to
figure that out from the documentation.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At present, BuildStream supports source-specific workspaces. This patch
makes workspaces element-wide. This will bring workspaces closer to what
the build area looks like inside the sandbox when the build actually
happens.
As part of this change, format of `.bst/workspaces.yaml` file will also
change. Previously, each element used to have a dict mapping each source
to its workspace directory. Now, each element will directly map to its
workspace directory.
If users have existing workspaces open, this patch tries to cope with it
but in some cases, it is not possible to reliably convert workspace
config from old format to new format. When an element has workspace open
for just one source, we assume that to be the workspace directory. But
if there were more than one workspaces associated with an element,
BuildStream will simply error out describing the issue.
Note that the actual contents of the workspace directory are not changed
in any case. So, if an element had multiple sources associated with it
but only had workspace open for source, the other sources will not be
automatically staged in the workspace unless the user runs `workspace
reset` or something equivalent.
Part of #209.
|
| |
|
|
|
| |
The 'ctx' parameter is carefully threaded through to 'complete_target',
but it doesn't actually use it. Remove the parameter from unused places.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This removes most of the usages of pkg_resources from the codebase, helping
the goal of getting rid of that completely.
With this change, version number is generated during install and embedded into
`__version__` which is then imported by root level `__init__`. From there,
it is used by other parts of the codebase when needed.
Generated `__version__` file is ignored and not tracked by git to prevent
unnecessary 'changes' messages and accidental commits of that file.
|
| |
|
|
|
|
|
| |
This change monkey patches setuptools' code generation functionality, so
that pkg_resources won't be imported in the generated file.
Fixes #172
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This was done so that the files can be re-used with different
project.conf.
|
| | |
|
| |
|
|
| |
staging artifacts
|
| |
|
|
|
|
|
|
|
| |
* Adds the 'overlap-whitelist' field to elements' public data. This is a
list of globs that match files that the element is allowed to overlap
other elements with.
* Adds the project-wide 'fail-on-overlaps' field. If set,
non-whitelisted overlaps will raise an error instead of printing a
warning.
|
