On 10 July 2018 at 12:52, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
in the meantime I managed to set up a template structure along with a script to construct job definitions suiting our needs. Thanks again for your help.
I have a further question: As far as I see, everyone seems to keep job definitions (or templates for those) and test definitions in separate repositories. Is there a certain reason for this? Why shouldn't I put job templates and test definitions that belong together side by side in the same folder?
I don't know of anything that should stop you from doing that. In our case we try to keep tests 'executor agnostic'. So they can be ran outside of LAVA and don't depend on any LAVA wrapper scripts. But that isn't something mandatory. So if you feel like locking your tests to LAVA you can do that.
Best Regards, milosz