Currently, the development of the Vagrant images relies on manual testing (I create scratch builds containing my changes and test them locally - due to hardware limitations, this means only testing with VirtualBox on an OS X host). Is it technically possible to automatically test the Vagrant images on ci.centos.org, using e.g. KVM via vagrant-libvirt? Perhaps we could add some sort of trigger on cbs.centos.org to trigger the tests, once a scratch build is successful?
Regards, Laurențiu
I wonder if there could be a vagrant plugin written for duffy. I've currently got linch-pin[1] working with duffy, but it's not a ruby module, but rather ansible. I'm not one to write it, but think it would also be valuable to my work.
Cheers,
herlo
1 - https://github.com/CentOS-PaaS-SIG/linch-pin
On Tue, Jul 26, 2016 at 2:32 AM, Laurentiu Pancescu lpancescu@gmail.com wrote:
Currently, the development of the Vagrant images relies on manual testing (I create scratch builds containing my changes and test them locally - due to hardware limitations, this means only testing with VirtualBox on an OS X host). Is it technically possible to automatically test the Vagrant images on ci.centos.org, using e.g. KVM via vagrant-libvirt? Perhaps we could add some sort of trigger on cbs.centos.org to trigger the tests, once a scratch build is successful?
Regards, Laurențiu _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Clint Savage -
Laurentiu Pancescu