On 06.04.2018 17:38, Frederic Lepied wrote:
On Fri, Apr 6, 2018 at 11:00 AM, Stef Walter <stefw(a)redhat.com
<mailto:stefw@redhat.com>> wrote:
Three reasons:
* dist-git repositories do not necessarily produce a package of the
same name. They usually do.
* dist-git repositories can produce multiple sub-packages, as you can
see in the case of cockpit. Any and all of those sub-packages should
be tested and/or gated by tests that live in that dist-git repo.
In this case there are 5 sub-packages from the cockpit dist-git repo in
the Atomic Host that should trigger the pipeline.
Although I understand current effort is on the All Package Pipeline, I
believe this might still be a problem going forward:
* There is no defined way to discover which dist-git repos to look for
tests related to a certain package in the standard test
specification.
Does that make sense? Dominik, did you have any ideas on how we might
fix this?
To solve this problem for rpm, we can use the Source RPM header to map
to a dist-git instead of using the rpm name.
Nice and clean. Anyone up for proposing the wording to add this to the
spec in the "Discovery" section?
Stef