This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/nested-ac-update
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 07a2aacf0 tests/integration/sandbox.py: Add test for
`action-cache-enable-update`
discard b44bda4ae sandbox: Add support for action cache updates via
`remote-apis-socket`
discard 119a36d6b ci: Update images
add 9c0b554c5 Implement loading of user provided provenance information
add d6d5e738c tests/frontend/show.py: Add SourceInfo test for user
provided data
add 8129838d4 Merge pull request #2009 from
apache/tristan/additional-source-provenance
add 0f939d66a ci: Update images
add ed6522f36 sandbox: Add support for action cache updates via
`remote-apis-socket`
add 62129a52c tests/integration/sandbox.py: Add test for
`action-cache-enable-update`
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (07a2aacf0)
\
N -- N -- N refs/heads/jbilleter/nested-ac-update (62129a52c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
doc/source/format_declaring.rst | 7 +-
src/buildstream/_loader/metasource.py | 7 +-
src/buildstream/_loader/types.py | 1 +
src/buildstream/element.py | 22 ++++++-
src/buildstream/source.py | 75 ++++++++++++++++++++--
src/buildstream/types.py | 36 +++++++++++
tests/frontend/show.py | 44 +++++++++++--
.../elements/{tar.bst => user-provenance.bst} | 3 +
8 files changed, 176 insertions(+), 19 deletions(-)
copy tests/frontend/source-info/elements/{tar.bst => user-provenance.bst} (58%)
