It would be really useful if one Provisioner could be shared across multiple Orchestrators in a way that would allow an Orchestrator to "return" non-destroyed systems back, for another Orchestrator to use.
That way, we'd get the benefits of Remote reuse of a single AdHocOrchestrator between tests, but on a multi-Orchestrator level.
Not very useful when each Orchestrator runs a different OS/arch version, but extremely useful for matrix testing, where all Orchestrators run on the same OS/arch, just with differently configured tests.
The current workaround is to construct a custom list of tests (ie. custom FMFTests) with multiple copies of every single test, with a name prefixed with the matrix combination.
/a=x,b=2/some/test
/a=x,b=2/another/test
...
/a=y,b=3/some/test
...
Using platforms for this would be cleaner/nicer.
It would be really useful if one Provisioner could be shared across multiple Orchestrators in a way that would allow an Orchestrator to "return" non-destroyed systems back, for another Orchestrator to use.
That way, we'd get the benefits of Remote reuse of a single AdHocOrchestrator between tests, but on a multi-Orchestrator level.
Not very useful when each Orchestrator runs a different OS/arch version, but extremely useful for matrix testing, where all Orchestrators run on the same OS/arch, just with differently configured tests.
The current workaround is to construct a custom list of tests (ie. custom FMFTests) with multiple copies of every single test, with a name prefixed with the matrix combination.
Using platforms for this would be cleaner/nicer.