[scl.org] validating scls being built

[Honza Horak]

On 10/11/2015 12:29 AM, Karanbir Singh wrote:
> 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 ?

Thanks, it seems fine to me for the beginning. Matej (cc'd) is also 
working on some basic sanity tests for collections, not sure how far he 
is and whether it would do the same (maybe a bit), but last time we 
checked the status it seemed he will have something pushed into [1] this 
week.

I've also added list of packages that we expect will be available for 
the rest of the collections [2]. It has slightly different format than 
yours, but a good thing is that we can share it with what we keep 
internally for a similar purpose..

[1] https://github.com/sclorg/sclo-ci-tests/
[2] https://github.com/sclorg/sclo-ci-tests/tree/master/PackageLists

Honza