[openstack-dev] [nova] CI report formatting (citrix / hyperv / vmware )

Sean Dague sean at dague.net
Thu Mar 26 09:59:41 UTC 2015


On 03/26/2015 03:41 AM, Gary Kotton wrote:
> 
> 
> On 3/25/15, 3:21 PM, "Sean Dague" <sean at dague.net> wrote:
> 
>> On 03/25/2015 09:03 AM, Gary Kotton wrote:
>>>
>>> From: Jordan Pittier <jordan.pittier at scality.com
>>> <mailto:jordan.pittier at scality.com>>
>>> Reply-To: OpenStack List <openstack-dev at lists.openstack.org
>>> <mailto:openstack-dev at lists.openstack.org>>
>>> Date: Wednesday, March 25, 2015 at 1:47 PM
>>> To: OpenStack List <openstack-dev at lists.openstack.org
>>> <mailto:openstack-dev at lists.openstack.org>>
>>> Subject: Re: [openstack-dev] [nova] CI report formatting (citrix /
>>> hyperv / vmware )
>>>
>>> Hi
>>> On Wed, Mar 25, 2015 at 12:39 PM, Sean Dague <sean at dague.net
>>> <mailto:sean at dague.net>> wrote:
>>>
>>>     Currently Citrix, HyperV, and VMWare CI systems reporting on Nova
>>>     patches have a different formatting than the standard that Jenkins
>>> and
>>>     other systems are using:
>>>
>>>     * test-name-no-spaces
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__link.to_result&d=AwIF
>>> aQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYB
>>> k8YTeq9N3-diTlNj4GyNc&m=WR2WbwJKtngJUjJEo4yFahEnv7RtC3NDaDsZFuzSukw&s=2Jr
>>> ZtoZF3o4ThkkR34bJH77FMeEorM65K2FQR9pKSuM&e=
>>>     
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__link.to_result&d=AwM
>>> FaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JY
>>> Bk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2k8XbFtgWlkcm_VdZCrFHTLEdiE&s=5S
>>> S-txUrD3o8KS3QIaCL3XMBbeCYK5CjmzmuxDda7Oc&e=>
>>>     : [SUCCESS|FAILURE] some
>>>     comment about the test
>>>
>>> I don't want to talk for Citrix, HyperV or VMWare but the "standard"
>>> only work if you use Zuul in your CI. I am using a setup based on a
>>> Jenkins plugin called gerrit-trigger and there's no way to format the
>>> message the way it's expected...
>>>
>>>
>>>     This means these systems don't show up in the CI rollup block -
>>>     
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__dl.dropbox.com_u_6514
>>> 884_screenshot-5F158.png&d=AwIFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNt
>>> Xt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=WR2WbwJKtngJUjJEo4
>>> yFahEnv7RtC3NDaDsZFuzSukw&s=47UEXfmar4lGrIce8bEgHwvws7Lw0DPGWdEzPSDDAXQ&e
>>> = 
>>>     
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__dl.dropbox.com_u_651
>>> 4884_screenshot-5F158.png&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMN
>>> tXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2
>>> k8XbFtgWlkcm_VdZCrFHTLEdiE&s=nIjYwznh1_8aVBSz-XVEJrpNaMsDfqyekOQ2IhiHTo8&
>>> e=>
>>>
>>>
>>> Current the Vmware CI will vote +1 iff the patch has passed on the CI.
>>> We can investigate adding this to the CI rollup block.
>>>
>>>
>>>
>>>     I'd really like that to change. The CI rollup block has been
>>> extremely
>>>     useful in getting the test results of a patch above the fold, and
>>> the
>>>     ability to dig into them clearly. I feel like if any CI system isn't
>>>     reporting in standard format that's parsible by that, we should
>>> probably
>>>     turn it off.
>>>
>>>
>>> I do not think that we should turn this off. They have value. It would
>>> be nice if things were all of the same format, which I guess that this
>>> is the intension of the mail. Lets all try and make an effort to work
>>> towards this goal.
>>
>> Right, honestly, I don't want these turned off, I want them reporting in
>> a more standard format. But I do think if they don't report in a
>> standard format it will cause problems and add to them being ignored.
> 
> Vmware Nova CI has been updated. Please see
> https://review.openstack.org/#/c/167713/ as an example. 

Great, thank you.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150326/07458f1e/attachment.pgp>


More information about the OpenStack-dev mailing list