08:00:17 <anteaya> #startmeeting third-party
08:00:18 <openstack> Meeting started Tue Jan 13 08:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:22 <openstack> The meeting name has been set to 'third_party'
08:00:34 <anteaya> anyone here for the third-party meeting?
08:03:11 <jyuso> anteaya: hi
08:03:17 <anteaya> hello jyuso
08:03:35 <anteaya> jyuso: how are things going?
08:04:15 <jyuso> anteaya: our CI is online few hours before.still many works to do:)
08:04:43 <anteaya> good for you!
08:04:57 <jyuso> anteaya: thanks
08:05:15 <anteaya> any questions or issues you want to talk about today?
08:06:38 <jyuso> anteaya: OK.I have a question about gerrit trigger
08:06:52 <anteaya> jyuso: great, ask away
08:08:02 <jyuso> The gerrit trigger would return such message to Gerrit "gerrit review <CHANGE>,<PATCHSET> --message 'Build Started <BUILDURL> <STARTED_STATS>' --verified <VERIFIED> --code-review <CODE_REVIEW>"
08:08:31 <anteaya> okay
08:09:43 <anteaya> what is your question about what gerrit trigger returns?
08:11:28 <jyuso> Yes.I saw some CI return more useful messages.Like URL,sign and many lines.If I want my messages become such pattern,Did that mean I just modify --message '' and it will worked?
08:12:09 <anteaya> well you need to make sure it does not report "Build Started"
08:12:34 <anteaya> #link http://ci.openstack.org/third_party.html#requirements
08:12:37 <amotoki> jyuso: as you may know, one CI should return one message per patchset.
08:12:38 <jyuso> yes,I've abandon "Build started".
08:13:02 <anteaya> A third-party system may only leave one comment per patch set (unless it is retriggered).
08:13:08 <anteaya> amotoki: thank you :D
08:13:25 <jyuso> amotoki: yes,I know that.thanks
08:13:33 <amotoki> jyuso: AFAIK there is no easy way to report multiple lines.
08:13:36 <anteaya> jyuso: so yes as amotoki says, you can only post a message to gerrit once the results are returned
08:13:57 <anteaya> let's take a look at some examples, shall we?
08:14:14 <anteaya> jyuso: can you find a patch that has a comment in the format you want to copy?
08:14:36 <jyuso> amotoki: oh,you mean I can't use Gerrit trigger to report multiple lines?
08:16:04 <jyuso> anteaya: Maybe this one https://review.openstack.org/#/c/135625/
08:16:50 <amotoki> jyuso: AFAIK yes
08:16:54 <anteaya> jyuso: which ci account should we look at?
08:17:23 <jyuso> anteaya: I think the partten of "IBM PowerKVM CI" is good.and they support us more usefule information
08:17:29 <anteaya> amotoki: do you use gerrit trigger?
08:17:51 <amotoki> anteaya: at first I used gerrit trigger, but soon after I migrated to zuul
08:18:19 <anteaya> jyuso: great well that makes it easy, krtaylor is an operator for IBM PowerKVM CI, ask him in -infra how to create that comment format
08:18:41 <anteaya> jyuso: he is in Texas
08:18:56 <amotoki> jyuso: I think most CIs including IBM CI use zuul. It is a format used by zuul report.
08:18:58 <anteaya> amotoki: does zuul allow you to customize your gerrit comments?
08:19:37 <amotoki> yes, but I think we can only customize the first line.
08:19:51 <anteaya> amotoki: really in zuul?
08:20:05 <anteaya> SergeyLukjanov: are you about?
08:20:05 <amotoki> yes. let me check
08:20:08 <jyuso> amotoki: Oh,thanks.I think that should be the reason.
08:20:50 <anteaya> jyuso: are you considering using zuul?
08:20:51 <jyuso> amotoki: I can't find out how to show such rich information with Gerrit triger:)
08:21:46 <jyuso> anteaya: oh,may be later.we don't need the nodepool script of zuul.
08:21:56 <anteaya> jyuso: okay
08:22:10 <jyuso> anteaya: our case is based on physical machine.each VM should be created with PCI device
08:22:25 <amotoki> we can customize message by using *-message in http://ci.openstack.org/zuul/zuul.html#pipelines
08:22:34 <anteaya> jyuso: well if using gerrit trigger limits what kind of comment you can generate, can you get by with customizing one line?
08:22:51 <anteaya> amotoki: thanks
08:23:02 <jyuso> anteaya: our comments is in that URL also.
08:23:10 <jyuso> vanteaya: very simple:(
08:23:29 <anteaya> jyuso: sorry which URL?
08:23:36 <anteaya> I seem to have lost track
08:23:51 <jyuso> amotoki: thanks.I'll check some details.
08:24:01 <jyuso> anteaya: https://review.openstack.org/#/c/135625/
08:24:56 <anteaya> jyuso: okay yes, so elminate: Patch Set 17:
08:24:58 <anteaya> Build Started
08:25:25 <anteaya> and Patch Set 18:
08:25:26 <anteaya> Build Successful http://198.175.100.33/135625/18
08:25:46 <anteaya> is perfectly fine
08:26:17 <anteaya> you have this message in your logs: Intel HW Based PCI CI
08:26:19 <jyuso> anteaya: yes.I've delete that "Build Started" after patch set 17:)
08:26:19 <anteaya> Intel PCI CI is based on physical machine,cover PCI pass-through and SRIOV testing.
08:26:21 <anteaya> The test cases running on this CI is located on Github repository.
08:26:23 <anteaya> Contact email:openstack_ci@intel.com
08:26:26 <anteaya> great thank you
08:26:46 <anteaya> and I think customizing your message in your logs is just fine
08:27:52 <jyuso> anteaya: OK,I think we should add such script info and wiki info into comments.It seems better
08:28:06 <anteaya> okay
08:28:16 <anteaya> I support more information
08:28:26 <anteaya> do investigate what is possible
08:28:36 <anteaya> gerrit trigger does have limitations
08:28:54 <amotoki> jyuso: my suggestion is to migrate to zuul once you have set up a basic functionality of your CI. zuul allows you to define trigger conditions easily and post better comment.
08:28:59 <jyuso> anteaya: yes.thanks.I'll.
08:29:03 <amotoki> The migration path is very simple:
08:29:22 <amotoki> setup zuul and remove gerrit trigger from your jobs.
08:30:37 <amotoki> another gerrit trigger limitation is it is not easy to support "recheck" trigger :(
08:30:59 <anteaya> amotoki: yes that is true
08:33:03 <jyuso> amotoki: Could I add messages which regexp "recheck"  into trigger condition of Gerrit trigger ?
08:33:37 <jyuso> amotoki: That's what I thought.but not try yet.
08:33:47 <amotoki> jyuso: iirc, we cannot.
08:34:15 <amotoki> but I thought arista shared a patch to support it.
08:34:47 <amotoki> I saw a mailing list post several months ago (one year?).
08:36:05 <anteaya> amotoki: yes I remember that
08:36:44 <jyuso> amotoki: ok...thank you.
08:38:01 <anteaya> #link https://wiki.openstack.org/wiki/Arista-third-party-testing
08:38:38 <anteaya> now the instructions are in a google doc, Sukhdev said he would try to get it transfered to the wikipage but that hasn't happened yet
08:40:05 <amotoki> jyuso: It is my blog post on zuul config and switching from gerrit trigger: http://ritchey98.blogspot.jp/2014/02/openstack-third-party-testing-how-to.html
08:40:37 <anteaya> #link http://ritchey98.blogspot.jp/2014/02/openstack-third-party-testing-how-to.html
08:40:38 <jyuso> amotoki: thanks:)
08:40:44 <anteaya> thanks for sharing that amotoki :D
08:40:50 <amotoki> jyuso: but note that zuul configuraiton is a bit old and the latst zuul with merger is not coming yet....
08:42:04 <amotoki> i need to update my CI master soon so i can update my post. feel free to ask me.
08:43:17 <jyuso> amotoki: thanks.I'll read your blog later.It looks like very useful:)
08:45:13 <jyuso> anteaya: thanks.I think I've got lots of useful information.my question is over:)
08:45:37 <anteaya> jyuso: thank you, I appreciate you letting me know
08:45:53 <anteaya> I'm glad you got some useful information
08:47:31 <anteaya> shall we discuss anything else?
08:47:41 <amotoki> nothing from me
08:47:55 <anteaya> amotoki: thanks for being here to answer questions
08:47:57 <anteaya> :D
08:48:01 <anteaya> I appreciate it
08:49:41 <jyuso> amotoki: thank you very much:)
08:49:53 <anteaya> would you like me to end the meeting so you can move onto other things?
08:49:57 <anteaya> I don't want to keep you
08:51:13 <anteaya> I'll end the meeting
08:51:14 <jyuso> anteaya: OK,i have no more question
08:51:20 <anteaya> thanks for attending
08:51:23 <jyuso> anteaya: thank you anteaya:
08:51:24 <anteaya> jyuso: okay great
08:51:29 <anteaya> see you next week
08:51:30 <amotoki> thanks all
08:51:34 <jyuso> anteaya: see you
08:51:36 <anteaya> thank you amotoki
08:51:42 <anteaya> #endmeeting