Jenkins job to run networking functional tests

[Giuseppe Vallarelli]

Hello everybody, following the previous discussion with Eyal,
I need to get rights in order to create a jenkins job to
achieve what stated in the subject.

Is it the right place for such request?

Cheers, Giuseppe

----- Forwarded Message -----
| From: "Eyal Edri" <eedri at redhat.com>
| To: "Giuseppe Vallarelli" <gvallare at redhat.com>
| Cc: "infra" <infra at ovirt.org>
| Sent: Sunday, August 18, 2013 2:06:22 PM
| Subject: Re: running network functional tests
| 
| Hi,
| 
| Usually in these cases when a new job is requested to a specific
| project/component,
| A 'power user' for the relevant team (in your case network), is given
| privileges on the Jenkins machine
| to add any job required.
| 
| I would propose the following:
|  1. request power user access to jenkins.ovirt.org (if you don't already
|  have)
|  2. add a new job with your functional test per commit (not per patch for
|  starts)
|     any infra member can assist you with the labels for slaves / os /etc...
|  3. once that job is running properly, you can contact infra to assist in
|  converting it to a per-patch job
|     with the topic / field verification logic done.
|  4. not sure if this is relevant to your tests, but all existing jenkins
|  slaves are VMs and not bare-metal.
| 
| i hope this helps.
| 
| Eyal.
| 
| ----- Original Message -----
| > From: "Giuseppe Vallarelli" <gvallare at redhat.com>
| > To: "infra" <infra at ovirt.org>
| > Sent: Friday, August 16, 2013 12:28:43 PM
| > Subject: Fwd: running network functional tests
| > 
| > ----- Forwarded Message -----
| > | From: "Giuseppe Vallarelli" <gvallare at redhat.com>
| > | To: "infra" <infra at ovirt.org>
| > | Cc: "David Caro Estevez" <dcaroest at redhat.com>
| > | Sent: Monday, August 12, 2013 10:58:04 AM
| > | Subject: running network functional tests
| > | 
| > | Hello everbody!
| > | Just recently we added networking functional tests and we would like
| > | to have them running when we submit patches network related, i.e.
| > | going to affect network modules. Displaying success or failure
| > | as it happens with the current unittests.
| > | 
| > | Requirements/ideas:
| > | 
| > | - OS Fedora 19/RHEL6.4 should not matter.
| > | 
| > | - Kernel module used: bonding, dummy.
| > | 
| > | - No more than one 'instance' of networkTests should run
| > |   on a specific host, simply because we use some global
| > |   constants to identify network name vlan id and so on.
| > | 
| > | - Ideally we can use a previously proposed idea of commit tag
| > |   where for example @networking is provided in the commit msg
| > |   title to identify the need of running also the network
| > |   functional tests.
| > | 
| > | - We should be able to run at the same time functional networking
| > |   tests and unit tests - I don't expect any conflicts.
| > | 
| > | Would be cool to have a test run before -1s all networking patches
| > | in case of problems :-)
| > | 
| > | Let me know if more information are needed.
| > | 
| > | 
| > | Cheers, Giuseppe
| > 
| > Is there any update on the subject?
| > 
| > Any estimate to have functional network tests running?
| > I mind that we can run network functional tests upstream
| > that will speed up our workflow and possibly decrease the
| > regressions.
| > 
| > Thanks Giuseppe
| > _______________________________________________
| > Infra mailing list
| > Infra at ovirt.org
| > http://lists.ovirt.org/mailman/listinfo/infra
| > 
|