Ramy, Thanks for providing the correct message. We will update our commit message accordingly.
Thanks, Nagendra Rao On Thu, Aug 13, 2015 at 4:43 PM, Asselin, Ramy <ramy.asse...@hp.com> wrote: > Hi Nagendra, > > > > Seems one of the issues is the format of the posted comments. The correct > format is documented here [1] > > > > Notice the format is not correct: > > Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: > http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/ > > Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] > some comment about the test > > > > Ramy > > > > [1] > http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit > > > > *From:* Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com] > *Sent:* Wednesday, August 12, 2015 4:37 PM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Cc:* brocade-openstack...@brocade.com > *Subject:* Re: [openstack-dev] [cinder] Brocade CI > > > > Mike, > > Thanks for your feedback and suggestions. I had send my response yesterday > but looks like didn't get posted on the lists.openstack.org. Hence > posting it here again. > > We reviewed your comments and following issues were identified and some of > them are fixed and some fix plans in progress: > > > 1) Not posting success or failure > > The Brocade CI is a non-voting CI. The CI is posting the comment for > build sucucess or failures. The report tool is not seeing these. We are > working on correcting this. > 2) Not posting a result link to view logs. > > We could not find any cases where CI is failed to post the link to logs > from the generated report. If you have any specific uses where it failed > to post logs link, please share with us. But we did see that CI not posted > the comment at all for some review patch sets. Root causing the issue why > CI not posted the comment at all. > 3) Not consistently doing runs. > > There were planned down times and CI not posted during those periods. > We also observed that CI was not posting the failures in some cases where > CI failed due non openstack issues. We corrected this. Now the CI should be > posting the results for all patch sets either success or failure. > > We are also doing the following: > > - Enhance the message format to be inline with other CIs. > > - Closely monitoring the incoming Jenkin's request vs out going builds and > correcting if there are any issues. > > > > Once again thanks for your feedback and suggestions. We will continue to > post this list on the updates. > > > Thanks & Regards, > > Nagendra Rao Jaladanki > > Manager, Software Engineering Manageability Brocade > > 130 Holger Way, San Jose, CA 95134 > > > > On Sun, Aug 9, 2015 at 5:34 PM, Mike Perez <thin...@gmail.com> wrote: > > People have asked me at the Cinder midcycle sprint to look at the Brocade > CI > to: > > 1) Keep the zone manager driver in Liberty. > 2) Consider approving additional specs that we're submitted before the > deadline. > > Here are the current problems with the last 100 runs [1]: > > 1) Not posting success or failure. > 2) Not posting a result link to view logs. > 3) Not consistently doing runs. If you compare with other CI's there are > plenty > missing in a day. > > This CI does not follow the guidelines [2]. Please get help [3]. > > [1] - http://paste.openstack.org/show/412316/ > [2] - > http://docs.openstack.org/infra/system-config/third_party.html#requirements > [3] - > https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Questions > > -- > Mike Perez > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev