We do not need gerrit-git-prep anymore, zuul-git-prep works on all our
slaves and has the advantage of using zuul-cloner so that the local
cache is used and Depends-On works.
Remove gerrit-git-prep and use zuul-git-prep instead everywhere.
Change-Id: I2f106af58f78fceaf3c497fe43e6f5a002695645
These projects don't have any code yet. Just shift their testing ahead
to Xenial so the testing is ready when the code arrives.
Change-Id: I933389d08d15c40428f507f9cd268e74d2fb2403
This is related to zuulv25, we make sure console-log is the last
publisher to ensure zuul-launcher logs are also uploaded.
Change-Id: I1616b97fad2b97fb9e977ec14543aab4bc673b58
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Beaker(puppet testing tool) has plugable hypervisor backends. Create one
project to manage the 'ssh to localhost' backend and one to hit the
nodepool api (rest or gear) remotely.
The aviator builders are here because they are actually just good solid
ruby tests. If this works out we can look at refactoring some generic
ruby test builders.
The beaker-localhost hypervisor backend can be used instead of the None
we are using now. This is more hygenic because we can specify exactly
how to behave instead of counting on fallback behaviour that may change.
There are some things this wont fix such as using ssh at all and
managing sshd_config. I've been talking about writing our own hypervisor
for several weeks now so I'd like to at least get it stubbed out as a
potential extention point.
The beaker-nodepool hypervisor might better live in stackforge/. It is a
hypervisor for beaker that interacts with the nodepool service to
provision nodes. I will likely use this with a standalone nodepool (no
zuul) for another project. It makes sense to keep this close to the
nodepool community(infra) but that isn't a technical requirement.
Change-Id: Iaad72a26b26a0ee89c4fd254d0bcb75535a8d551
Monty Taylor