Use TEST_SUBJECTS to specify the extra packages.
ex:
export TEST_SUBJECTS="docker:docker.io/library/fedora:27 /home/fred/RPM/RPMS/x86_64/systemd-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm /home/fred/RPM/RPMS/x86_64/systemd-libs-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm /home/fred/RPM/RPMS/x86_64/systemd-pam-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm"
Fixes: #106
why not adding a task to install those packages in your playbook?
Fedora vs. CentOS/RHEL
I would propose to stick to https://fedoraproject.org/wiki/Changes/InvokingTests
There is a definition:
Test Subject: The items that are to be tested. Examples: RPMs, OCI image, ISO, QCow2, Module repository ...
In this case Test Subject is: Docker image. New RPMs are not test subject.
Let's keep clear and easy to understand workflow.
I would go for: clear and transparent and independent step: preparing TEST_SUBJECT.
Do not squash two task into one. This will bring more confusion.
@ttomecek, @astepano see the context for this PR in https://pagure.io/standard-test-roles/issue/106
Use TEST_SUBJECTS to specify the extra packages.
ex:
export TEST_SUBJECTS="docker:docker.io/library/fedora:27 /home/fred/RPM/RPMS/x86_64/systemd-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm /home/fred/RPM/RPMS/x86_64/systemd-libs-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm /home/fred/RPM/RPMS/x86_64/systemd-pam-236-0.1.20171207151953.e97b7b5.fc27.x86_64.rpm"
Fixes: #106