| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
it was self.linux32 in places and self._linux32 in others.
|
| |\
| |
| |
| |
| | |
Prepare for 1.6.1
See merge request BuildStream/buildstream!2096
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Fix import of BlobNotFound
See merge request BuildStream/buildstream!2083
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
git source plugin: Fix check for remote existence
See merge request BuildStream/buildstream!2030
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When checking whether a remote exists in the cached git repository, we
currently perform a substring match on the output of 'git remote'.
This fails when there is an existing remote name that contains the
name we're looking for.
This was fixed by the rewrite of git fetching in !1808, but that
change seems unsuitable for the stable 1.4 branch.
Instead, split the command output into a list and check that the
remote name is in the list.
Closes #1372.
|
| | |
|
| |\
| |
| |
| |
| | |
[bst-1] cascache.py: allow using Remote Asset for storing refs
See merge request BuildStream/buildstream!2000
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
element.py: add configuration for sandbox architecture and os
See merge request BuildStream/buildstream!1934
|
| | |
| |
| |
| |
| |
| | |
only allow builds of the same os and architecture and 32-bit on 64-bit
based on e5d8c7d8a0ddbee8ff14 and b0603fb014c51660860c
|
| |/
|
|
| |
based on 1ad35fcd1bbb4a89e177da44303cf95e5a3b659d
|
| |\
| |
| |
| |
| | |
cascache.py: enable grpc keepalive pings
See merge request BuildStream/buildstream!1979
|
| |/
|
|
|
| |
This allows bst to detect when connections are dropped instead of hanging
indefinitely
|
| |\
| |
| |
| |
| | |
Split up artifact cache and CAS cache
See merge request BuildStream/buildstream!1969
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes CASCache from a subclass to a delegate object of
ArtifactCache. As the lower layer, CASCache no longer deals with
elements or projects.
Based on 626d20aefb52d25d987c61f377cc1ce3172da8c3
Fixes #659.
|
| | |
| |
| |
| |
| |
| |
| | |
The artifact cache backend does not affect build outputs and we anyway
no longer have pluggable artifact cache backends. This hardcodes
CASCache instead of removing the entry completely to avoid cache key
changes.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Get the artifact cache from the context instead.
|
| | |
| |
| |
| |
| | |
get_artifact_fullname() is required to construct the ref. The cache key
alone does not suffice.
|
| |/
|
|
|
| |
os.utime() updates both, however, list_artifacts() sorts refs by mtime,
i.e., atime is irrelevant.
|
| |\
| |
| |
| |
| | |
Append lists when merging conditional statements (bst-1)
See merge request BuildStream/buildstream!2003
|
| | |
| |
| |
| |
| |
| | |
Added tests to ensure that conditional statements don't get overwritten
when performing composition of one dictionary on top of another due to
include processing.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During composition of project.conf, it can happen that we
are including and composing node hierarchies before options
are resolved and before we are ready to evaluate conditional
statements.
Without this patch, conditional statements are treated like
regular lists, causing existing conditional statements to
be overwritten by subsequently composited conditional statements
without ever having been resolved.
This patch introduces a special case for composing lists,
when composing a sequence that is a conditional statement, the
sequence is appended instead of overwriting the underlying
list.
Note that precedence of declarations in including vs included
yaml fragments did raise some concern, and a test in the following
commit is added to cover this case. Composition of conditional lists
on top of other conditional lists are unconditionally appended,
however the semantics of includes ensures that the including fragment's
conditionals is always composited *on top* over the included fragment,
ensuring that we have the correct pecedence even when compositing
yet to be resolved conditional directives.
|
| |
|
|
|
|
|
|
|
| |
As per this announcement regarding formalizing committers:
https://mail.gnome.org/archives/buildstream-list/2020-May/msg00023.html
We are now using a CODEOWNERS file to ensure only maintainers can
greenlight patches for protected branches in gitlab.
|
| |\
| |
| |
| |
| | |
Variables non-recursive and lazy resolution refactor (bst-1)
See merge request BuildStream/buildstream!2001
|
| | |
| |
| |
| |
| | |
Ensure that we get the expected provenance when expanding a variable
included in an overlap whitelist entry.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Test scenarios where a junction needs to resolve variables
in order to configure a subproject, but where some other variables
may be derived from the same subproject.
In this scenario we allow partial resolution of variables
for junction elements.
* Enhanced the undefined variables and circular reference tests
to also check for the expected provenances.
* Test for deep variable resolution
Test variable indirection with 50, 500 and 5000 variables:
* 50 - tests generally large indirections in the recursive algorithm,
which is limited to 200 recursions
* 500 - tests that the non-recursive algorithm works for successful outcomes
and not only for error resolution
* 5000 - tests that the iterative algorithm works and ensures it
is not discarded, as a recursive algorithm cannot be implemented
to support this depth with python (which limits itself to
merely 1000 stack frames).
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rebasing bst-1 variables code on bst-2 cython version, without the cython.
This is mostly a drop in replacement, except that:
* Now calls to Variables.subst() must provide the passed string's Provenance
* Elements must now call Variables.check() explicitly
This commit also adds a test to ensure that junctions can use partially
resolved variables, even when the calling project would require that all
variables be resolved in order to completely be resolved. Resolving variables
within junctions is allowed so long as those variable resolutions do not
require variable values from the target project they are junctioning.
|
| |\
| |
| |
| |
| | |
Update mailing list (bst-1)
See merge request BuildStream/buildstream!1981
|
| |/
|
|
|
|
| |
Next time there is a bst-1 release, the mailing list in related
documentation will be updated (also if anyone is browsing the bst-1
branch in git).
|
| |\
| |
| |
| |
| | |
Support version specific configuration files
See merge request BuildStream/buildstream!1945
|
| | | |
|
| | | |
|
| |/
|
|
|
|
| |
Allow users to keep separate buildstream.conf files in their
XDG_CONFIG_HOME for separate BuildStream versions, in case they
have BuildStream 1 and 2 installed.
|
| | |
|
| |\
| |
| |
| |
| | |
Detect non BuildStream 1 projects and plugins
See merge request BuildStream/buildstream!1923
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
From BuildStream 2, we added BST_MIN_VERSION which must be specified by
all plugins. This new assertion in BuildStream 1 detects the presence of this
in order to issue an early assertion informing the user that they should
use BuildStream 1 plugins for BuildStream 1 projects.
|
| | | |
|
| | | |
|
