@richm I suggest to store plans in roles' repositories. The advantages are:
It is clearer for users to see the plan in place, even though the test that this plan runs is stored remotely.
Roles that require special-case multihost plans, can store those plans locally in the repo too.
It will be possible to run plans with tmt try or tmt run locally. The test requires some changes for this to work, because currently it clones the repo and checks out a PR. And for this scenario, test must run from local changes.
I will test this with mssql for now to avoid changing rhel-system-roles repos.
We will need to remove the plans dir in specs. I don't think it will break something, but it is not required in RPMs.
@richm I suggest to store plans in roles' repositories. The advantages are:
tmt try
ortmt run
locally. The test requires some changes for this to work, because currently it clones the repo and checks out a PR. And for this scenario, test must run from local changes.I will test this with
mssql
for now to avoid changing rhel-system-roles repos.We will need to remove the
plans
dir in specs. I don't think it will break something, but it is not required in RPMs.