Roman Shaposhnik Konstantin Boudnik to add more context.
How this sort of off-beat idea came about
- When roman was travelling, we discussed how for the CI we could easily use the bigtop-deploy/vm/docker-puppet recipes evans wrote, to test stuff.
- At that point, iirc, cos mentioned : We should add vagrant to bigtop toolchain, so installation was taken for granted and we could leverage that wherever we wanted to, however we wanted to.
My 2 cents
Although not required per se itd be great to run the vagrant-docker recipes in the CI , after all
- thats the easiest way for users to spin up bigtop ,and so good to autotest it works perfectly.
- and now that we can run vagrant to read rpms from output/ , vagrant-docker can be used to test the components that are built from source, for free , so saves us some duplicate work on the CI.
In any case — this is mostly Roman Shaposhnik's decision i think, as he's the ci maintainer right now. so he knows best wether it will be something he would like to use in jenkins.