Hi, we have been using our testing framework (Javapackages Validator - JPV) for testing Java packages for quite some time and it works well on single package pull requests. JPV does static analysis of RPM files after they have been built. For Fedora pull requests, the Testing farm puts the RPMs into a directory `/var/share/test-artifacts`. Problem is that when doing side tag builds, the RPMs of all the components are present together and there is no way for the tool to distinguish which package it is supposed to test.
We have a minimal test plan present in every Java package we maintain. Example: https://src.fedoraproject.org/rpms/junit5/blob/rawhide/f/plans/javapackages....
Example of a failed side-tag test: * https://bodhi.fedoraproject.org/updates/FEDORA-2026-ef76680eea * https://artifacts.dev.testing-farm.io/11bb820b-7faa-4263-b2f2-7c6ccf214b67/ (The test should have only tested for `junit5` RPMs and files inside).
The question is: is there some environment variable or metadata available for the TMT tests where the test / plan can see where it came from? In this case from the dist-git of the package `junit5`.
-
Marián Konček