Signed-off-by: Michal Srb michal@redhat.com
rebased onto 3f2441b86f620e08df7666245603c0c58516a248
Build succeeded.
I'm not sure there is a guaranty that the first occurrence is the repo artifact of the current package because we will get multiple repo artifact in that list in case of multiple "Depends-on" on rpms/ repos.
Here https://pagure.io/zuul-distro-jobs/blob/master/f/roles/repo-setup/tasks/main.yaml you'll find an example about how to extract the repo artifact of the rpms being tested.
To that extends can tmt handle multiple repo artifacts ? Does it make sense in case of multiple "Depends-on" on rpms repos ?
Is there a way how to filter out all the depends-on repo artifacts? Or a way how to identify repo that was created for the specific MR for which the pipeline is running?
Oh, wait, re-reading the URL that you shared, I think I see how to do it.
rebased onto fea4f067d6a890dcf59d0f2bdce502fd27fa2526
Updated.
Metadata Update from @fbo: - Pull-request tagged with: gateit
Metadata Update from @fbo: - Pull-request untagged with: gateit
recheck
Build succeeded (gate pipeline).
Pull-Request has been merged by zuul
Signed-off-by: Michal Srb michal@redhat.com