7 Commits

Author	SHA1	Message	Date
mprahl	d54422adeb	Don't filter RPMs of reused components from a module that depends on itself ... If a module has filters set and it buildrequires itself, issues occur during component reuse. In that event, the filtered RPMs from the previous module build will not be available in the buildroot because the NVRs in the filters will match the RPMs from the reused component. Co-authored-by: Jan Kaluza <jkaluza@redhat.com>	2018-08-13 11:13:40 -04:00
mprahl	f422b82ce7	Make _get_reusable_module a public method so it can be used elsewhere	2018-08-09 19:25:35 -04:00
mprahl	411e459008	Use the actual name from the NVR instead of component.package when reusing components ... The name from the NVR and the name from the component may be different based on the macros being used as part of the build. SCLs are a great example of this.	2018-08-07 10:34:09 -04:00
mprahl	a78c564073	Revert "Store the component's build ID and use that to identify the build when acting on a tag message" ... This reverts commit 9bd16beeef.	2018-08-07 10:32:50 -04:00
mprahl	9bd16beeef	Store the component's build ID and use that to identify the build when acting on a tag message ... This resolves an issue where the component name is different than the package being tagged due to a macro such as those used for SCLs.	2018-08-03 20:45:00 -04:00
Jan Kaluza	8d1d439737	Generate 'context' from hash based on buildrequires/requires stream. Reuse components only from module with the same stream_build_context.	2018-04-24 15:45:26 +02:00
Jan Kaluza	9b6fd2ba39	Split utils.py to multiple files based on the methods use-case.	2018-04-03 09:58:57 -04:00