Open Stack

Andy and Kyle,

Once the patch [1] is merged, we can re-verify ODL CI and then deciding
about the re-enable part.
At this moment ODL CI is even failing for your patch.
https://jenkins.opendaylight.org/ovsdb/job/openstack-gerrit/2782/


Thanks,

Edgar

On 11/21/14, 9:31 AM, "Kyle Mestery" <mestery at mestery.com> wrote:

>On Fri, Nov 21, 2014 at 11:30 AM, Edgar Magana <edgar.magana at workday.com>
>wrote:
>> This is bothering me about the tests results:
>> 
>>https://jenkins.opendaylight.org/ovsdb/job/openstack-gerrit/2806/artifact
>>/o
>> dl_tempest_test_list.txt
>>
>>
>> The status is PASSED when this show a test failed!
>>
>Agreed, this is fixed with the more recent version of OpenDaylight
>(Helium.1), which I have a patch up for here [1].
>
>Still, this is worth noting.
>
>Thanks,
>Kyle
>
>[1] https://review.openstack.org/#/c/134309/
>
>> Edgar
>>
>> On 11/21/14, 9:19 AM, "Andrew Grimberg" <agrimberg at linuxfoundation.org>
>> wrote:
>>
>>>On Fri, 2014-11-21 at 17:16 +0000, Doug Wiegley wrote:
>>>> > On Nov 21, 2014, at 9:57 AM, Andrew Grimberg
>>>><agrimberg at linuxfoundation.org> wrote:
>>>> >
>>>> > On Fri, 2014-11-21 at 16:44 +0000, Doug Wiegley wrote:
>>>> >
>>>> >> I checked out their CI results, and it's behaving well enough that
>>>> >> gerrit access shouldn't be harmful.
>>>> >>
>>>> >> The test build can be seen off of this review:
>>>> >> https://review.openstack.org/#/c/136142/
>>>> >>
>>>> >> The only real issue that I saw was that the results link doesn't go
>>>>to
>>>> >> a logs directory as defined here:
>>>> >>
>>>>https://wiki.openstack.org/wiki/NeutronThirdPartyTesting#Log_.26_Test_R
>>>>es
>>>>ults_Filesystem_Layout
>>>> >
>>>> > Doug,
>>>> >
>>>> > Thanks for the link. If the current logs tarball was exploded out
>>>> > directly on the Jenkins archive links would that be better? Kyle,
>>>>you
>>>> > may want to consider modifying the final log archival composition of
>>>>the
>>>> > job.
>>>>
>>>> I think the common thing to do is to have a post-build step that dumps
>>>>your artifacts onto a generic web server somewhere, with on-the-fly
>>>>decompression enabled if you want to store .gz's, and then link to that
>>>>directory in gerrit, instead of linking to jenkins.
>>>>
>>>> For example, this:
>>>>
>>>> 
>>>>http://jenkins.a10cloud.com/job/a10-neutron-tempest/lastSuccessfulBuild
>>>>/
>>>>
>>>> ... becomes a link to this:
>>>>
>>>> http://ci.a10cloud.com/logs/a10-neutron-tempest/136248/7/5114/
>>>
>>>We're definitely working towards that. Haven't managed to get everything
>>>in place to handle it though :-/
>>>
>>>Then again, outside of our integration with OpenStack we haven't had a
>>>lot of call for that since our Jenkins is open to the world to see
>>>including how the jobs are configured.
>>>
>>>-Andy-
>>>
>>>--
>>>Andrew J Grimberg
>>>Systems Administrator
>>>The Linux Foundation
>>
>>
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>
>_______________________________________________
>Third-party-announce mailing list
>Third-party-announce at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce