[Gluster-devel] Adding more jobs to test Gluster regularly
Niels de Vos
ndevos at redhat.com
Wed Jun 29 10:33:08 UTC 2016
[and yes, NOW with gluster-devel-on CC, sorry for the duplicate]
[changed subject and added gluster-devel on CC]
On Wed, Jun 29, 2016 at 05:37:17AM +0530, Sankarshan Mukhopadhyay wrote:
> On Tue, Jun 28, 2016 at 9:45 PM, Niels de Vos <ndevos at redhat.com> wrote:
> > Coincidentally I've asked Humble about the option to provide a container
> > (and maybe VM) image through the CentOS Storage SIG. Just as with the
> > packages, we should try to utilize the integration with different
> > distributions.
> I agree. Containers (and even VM) images are build-time artifacts
> which we should produce and make available in a regular manner.
> I have a follow-up question on the production of these artifacts -
> when do we check whether the RPMs or, the images produced are sane?
> For example, that the RPMs are packaged well and as per specifications
Well, the RPMs can have different guidelines depending on the
distribution they are made for. So the official RPMs are packaged in
Fedora , CentOS Storage SIG  and other distribution specific
repositories. The distributions are responsible for verification of the
packages they ship.
But, we could do something like this for the included .spec. The nightly
builds  can be consumed by other tests. It is possible to download
the RPMs and run "rpmlint" and other verification tools on them. It is
relatively straight forward to write a script that we can include as a
job in the CentOS CI . The gluster_libgfapi-python script  can be
taken as an example.
Anyone is more than welcome to send me scripts that I can wrap in the
needed CentOS CI Jenkins environment. Depending on the time that the
tests need, we can run them every night, week, or whatever. If needed we
can run them upon each patch submission, but we'll probably need to
request a higher resource limit in that case.
I guess you could request an RPM-verification test , but please add
some details on what tools you would like to see used. At the moment
there are very few contributors helping out with the running of
automated tests, so do not have too high expectations on when someone
gets around to write+test a script from scratch.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the Gluster-devel