On 10/24/2014 07:18 PM, John Dulaney wrote:
>> How to deliver tests? a/ just use them directly from git (we
>> to keep some metadata for dependencies anyway) b/ package them as
>> RPMs (we can keep metadata there; e.g. Taskotron will run only
>> tests that have "Provides: ci-tests(mariadb)" after mariadb is
>> built; we also might automate packaging tests to RPMs)
To answer both of these, the plan is to keep taskotron tasks in their own
git repo; currently this is at (0).
To run the tasks, taskotron sets up a disposable task client and then git
clones the task to be run. This solves the issue of delivery and allows
a continuous integration-like solution.
I mentioned it in a different mail in this thread (just sent), but just
TL;DR version of it -- I think we should keep tests away from Taskotron
itself, even if they will be run by it.