[scl.org] validating scls being built
Subhendu Ghosh
sghosh at redhat.com
Sun Oct 11 02:21:51 UTC 2015
It would also be useful if the repo definitions did not use ReleaseVersion to allow use by CentOS and other distroa.
Sent from Nine
From: Karanbir Singh <mail-lists at karan.org>
Sent: Oct 10, 2015 6:29 PM
To: centos-devel at centos.org; sclorg at redhat.com
Subject: [scl.org] validating scls being built
firstly, apologies for the cross post.
I've setup an example to illustrate some very simple things we can do to
validate a collection. In this case the vagrant collection.
https://github.com/kbsingh/validate-vagrant-scl has the test script.
It does 2 things:
1) makes sure all the rpms we expect to have in the repo are there.
2) it will install the collection, run a centos/7 vagrant box, and run
the centos functional test suite inside the box. if this passes, we can
assert that vagrant installed ok, was able to run a libvirt backed box
properly, and was able to provide typical expected functionality.
There maybe 100s more features of the collection we are not testing
here, but that might not be needed if a simple baseline is established.
And this test can be run, from triggers in ci.centos.org, watching the 3
repos we care about for the vagrant collection ( ruby22 / ror41 and
vagrant itself ).
thoughts ?
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
_______________________________________________
SCLorg mailing list
SCLorg at redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/sclorg/attachments/20151010/d35ef9d5/attachment.htm>
More information about the SCLorg
mailing list