Re: [vdsm] Jenkins testing.

2012-08-21 Thread Robert Middleswarth
On 08/22/2012 12:03 AM, Deepak C Shetty wrote: On 08/22/2012 07:40 AM, Robert Middleswarth wrote: On 08/14/2012 04:54 AM, Deepak C Shetty wrote: On 08/14/2012 12:52 PM, Deepak C Shetty wrote: On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per

Re: [vdsm] Jenkins testing.

2012-08-21 Thread Deepak C Shetty
On 08/22/2012 07:40 AM, Robert Middleswarth wrote: On 08/14/2012 04:54 AM, Deepak C Shetty wrote: On 08/14/2012 12:52 PM, Deepak C Shetty wrote: On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oV

Re: [vdsm] Jenkins testing.

2012-08-21 Thread Robert Middleswarth
On 08/14/2012 04:54 AM, Deepak C Shetty wrote: On 08/14/2012 12:52 PM, Deepak C Shetty wrote: On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli. There are 3 st

Re: [vdsm] Jenkins testing.

2012-08-21 Thread Itamar Heim
On 08/14/2012 10:22 AM, Deepak C Shetty wrote: On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli. There are 3 status a patch can get. 1) Success - Means the pat

Re: [vdsm] Jenkins testing.

2012-08-14 Thread Dan Kenigsberg
On Tue, Aug 14, 2012 at 01:43:06AM -0400, Robert Middleswarth wrote: > After a few false starts it looks like we have per patch testing > working on VDSM, oVirt-engine, oVirt-engine-sdk and > oVirt-engine-cli. There are 3 status a patch can get. 1) Success - > Means the patch ran though the tests

Re: [vdsm] Jenkins testing.

2012-08-14 Thread Deepak C Shetty
On 08/14/2012 12:52 PM, Deepak C Shetty wrote: On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli. There are 3 status a patch can get. 1) Success - Means the

Re: [vdsm] Jenkins testing.

2012-08-14 Thread Deepak C Shetty
On 08/14/2012 11:13 AM, Robert Middleswarth wrote: After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli. There are 3 status a patch can get. 1) Success - Means the patch ran though the tests without issue. 2) Fa

Re: [vdsm] Jenkins testing.

2012-08-14 Thread Eyal Edri
Great job! I know it required a great effort and time to make this work so kudos for making it happen. Eyal. - Original Message - > From: "Robert Middleswarth" > To: "infra" , engine-de...@ovirt.org, "VDSM Project > Development" > , "arch" > Sent: Tuesday, August 14, 2012 8:43:06 AM

[vdsm] Jenkins testing.

2012-08-13 Thread Robert Middleswarth
After a few false starts it looks like we have per patch testing working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli. There are 3 status a patch can get. 1) Success - Means the patch ran though the tests without issue. 2) Failure - Means the tests failed. 3) Aborted - Gener