May I apply for a user account on jenkins.ovirt.org to run VDSM functional tests?

[Eyal Edri]

----- Original Message -----
> From: "Dan Kenigsberg" <danken at redhat.com>
> To: "Eyal Edri" <eedri at redhat.com>, "Zhou Zheng Sheng" <zhshzhou at linux.vnet.ibm.com>,
> vdsm-devel at lists.fedorahosted.org, infra at ovirt.org
> Sent: Tuesday, January 29, 2013 2:07:58 PM
> Subject: Re: May I apply for a user account on jenkins.ovirt.org to run VDSM functional tests?
> 
> On Tue, Jan 29, 2013 at 12:21:46PM +0100, Ewoud Kohl van Wijngaarden
> wrote:
> > On Tue, Jan 29, 2013 at 06:15:08AM -0500, Eyal Edri wrote:
> > > ----- Original Message -----
> > > > From: "Zhou Zheng Sheng" <zhshzhou at linux.vnet.ibm.com>
> > > > To: infra at ovirt.org
> > > > Cc: "ShaoHe Feng" <shaohef at linux.vnet.ibm.com>
> > > > Sent: Tuesday, January 29, 2013 12:24:27 PM
> > > > Subject: May I apply for a user account on jenkins.ovirt.org to
> > > > run VDSM	functional tests?
> > > >
> > > > Hi all,
> > > >
> > > > I notice there is no VDSM functional tests running in oVirt
> > > > Jenkins.
> > > > Currently in VDSM we have some XML-RPC functional test cases
> > > > for
> > > > iSCSI,
> > > > localfs and glusterfs storage as well as creating and
> > > > destroying VMs
> > > > on
> > > > those storage. Functional tests through JSON-RPC are under
> > > > review. I
> > > > also submit a patch to Gerrit for running the tests easily
> > > > (http://gerrit.ovirt.org/#/c/11238/). More test cases will be
> > > > added
> > > > to
> > > > improve test coverage and reduce the chance of regression.
> > > >
> > > > Some bugs that can not be covered by unit test can be caught by
> > > > functional tests. I think it would be helpful to run these
> > > > functional
> > > > tests continuously. We can also configure the Gerrit trigger in
> > > > Jenkins
> > > > to run functional tests when someone verifies the patch or when
> > > > it
> > > > gets
> > > > approved but not merged. This may be helpful to the maintainer.
> > > >
> > > > I've setup a Jenkins job for VDSM functional tests in my lab
> > > > server.
> > > > You
> > > > can refer to the job configuration of my current setup
> > > > (https://github.com/edwardbadboy/vdsm-jenkins/blob/master/config.xml).
> > > > After my patch in Gerrit is accepted, the job configuration
> > > > will be
> > > > simpler and the hacks can be removed. May I apply a user
> > > > account for
> > > > creating job in the oVirt Jenkins?
> > > >
> > >
> > > Hi Zhou,
> > > Basically there shouldn't be any problem with that.
> > > we have an option for giving a 'power-user' permissions for
> > > certain
> > > users on oVirt misc projects to add and and configure jobs for
> > > thier
> > > project.
> > >
> > > it requires knowledge in jenkins, which it seems that you have
> > > and
> > > recognition from the team/other developers from the relevant
> > > project
> > > (in this case, VDSM) that you are an active member of the
> > > project.
> > > (just a formality essentially)
> > >
> > > I've added engine-devel list to this thread so anyone from vdsm
> > > team
> > > can vote +1 for adding you as a power user for jenkins.
> > >
> > > once we'll receive a few +1 and not objections i'll create a user
> > > for
> > > you and send you the details.
> > >
> > 
> > I think vdsm-devel is more relevant here.
> 
> Zhou has a lot of credibility in vdsm-devel, but we have a watchful
> eye
> here as well.
> 
> Yes, I'd be proud to endorse Zhou as a Jenkins power user. I would
> only
> like to warn that we must make sure that no more than one functional
> test
> is being run per slave - vdsm process are quite primadonic. Is there
> a
> Jenkins mechanism to ensure that only one job (of a certain job
> class)
> is running on a specific host?

yes there is, it's a default behavior, and if you enable concurrent jobs, you need to make sure to allow only 1 job per node.

> 
> All and all, big +1.
> 
>