-
Notifications
You must be signed in to change notification settings - Fork 40
Support multi source source provenance info #2098
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multi source source provenance info #2098
Conversation
2064cf3 to
2b0267c
Compare
2b0267c to
84d65c5
Compare
84d65c5 to
835981f
Compare
|
Do plugins need access to the actual |
|
Yup, taking in to account #2095 (comment), there's no need to expose SourceProvenance to achieve this. |
835981f to
bbc05ba
Compare
|
I've updated this branch as per my previous comment, but this still requires a test. |
bbc05ba to
4a04dac
Compare
4a04dac to
89c724f
Compare
89c724f to
6824dde
Compare
6824dde to
4cb1852
Compare
This allows multi-source source plugins to provide this information per source rather than as a singular top level. This is done by adding a `provenance_node` parameter to `create_source_info()` that when specified overrides the use of the source's top level source provenance info. Co-authored-by: Joshua Zivkovic <joshua.zivkovic@codethink.co.uk>
4cb1852 to
8409e5d
Compare
8409e5d to
84e490e
Compare
Fixes #2073
This PR provides a way for multi-source plugins to provide source provenance info in their own way instead of only the top level source source info being used.
This is done by exposing the optional
source_provenance_attrsargument tocreate_source_info()which when used overrides the usage of the default provenance for a source. Any plugin that needs to parse provenance in it's own way can then supply it's results using this. This has been trialled with thecargo2source plugin in https://gitlab.com/BuildStream/buildstream-plugins-community/-/merge_requests/408.