15:00:11 <anteaya> #startmeeting third-party
15:00:11 <openstack> Meeting started Mon Feb  1 15:00:11 2016 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:15 <openstack> The meeting name has been set to 'third_party'
15:00:18 <anteaya> hello
15:00:27 <eantyshev> Hello!
15:00:33 <lennyb> hi
15:00:46 <anteaya> hello eantyshev and lennyb
15:00:50 <anteaya> how are you today?
15:01:26 <eantyshev> Last week I discovered that periodic pipelines don't work in current zuul
15:01:46 <anteaya> eantyshev: that is good to know
15:01:53 <anteaya> how did you discover that?
15:02:01 <mmedvede> hi
15:02:07 <anteaya> hey mmedvede
15:02:17 <eantyshev> got a quick fix for that: https://review.openstack.org/#/c/272123/
15:02:19 <anteaya> mmedvede: thank you for chairing last week's meeting
15:02:25 <anteaya> mmedvede: how did it go?
15:02:47 <eantyshev> anteaya: just tried to establish a periodic job in our CI
15:02:47 <mmedvede> anteaya: you are welcome. It went good
15:03:17 <anteaya> #link fix zuul's processing of periodic pipeline https://review.openstack.org/#/c/272123/
15:03:23 <anteaya> eantyshev: awesome, thank you
15:03:31 <anteaya> mmedvede: I'm glad to hear that
15:03:33 <anteaya> :)
15:03:49 <anteaya> does anyone else have a periodic pipeline for their ci?
15:03:54 <anteaya> or tried to set one up?
15:04:08 <mmedvede> anteaya: we do. But we are using pinned zuul version
15:04:42 <eantyshev> anteaya: I also had periodic pipelines some time ago, and it worked then
15:04:51 <anteaya> mmedvede: which zuul version?
15:05:08 <anteaya> eantyshev: okay great, so this is a regression as you point out in your commit message
15:05:14 <anteaya> thanks for including that history
15:06:10 <anteaya> so reviewing eantyshev's patch will be helpful
15:06:14 <anteaya> thanks eantyshev
15:06:26 <anteaya> does anyone have anything else they would like to discuss today?
15:06:29 <eantyshev> if nobody minds, I'll make another proposal, for ciwatch
15:06:45 <anteaya> eantyshev: you have the floor
15:06:48 <eantyshev> https://review.openstack.org/#/c/274412
15:07:25 <mmedvede> eantyshev: I would look at this first thing
15:07:38 <anteaya> #link patch to add ciwatch filtering by project: https://review.openstack.org/#/c/274412
15:07:45 <eantyshev> this helps us to compare selected jobs of Jenkins (like dsvm-tempest-full) with our CI results
15:07:59 <anteaya> nice
15:08:09 <anteaya> I think that is a feature others have wanted as well
15:08:21 <anteaya> I hope your patch is well recieved
15:08:50 <eantyshev> mmedvede: I'm new to jquery etc., so I expect certain corrections
15:09:10 <eantyshev> thanks, anteaya
15:09:40 <anteaya> thank you for offering the patch
15:09:50 <anteaya> does anyone have anything more to share on this topic?
15:09:51 <lennyb> I have a question regarding ciwatch - does it support REST query?
15:10:09 <mmedvede> eantyshev: ciwatch is missing many features at the moment. And we decided to concentrate on refactoring codebase first. But we should not stop from improving it, and thank you for the patch
15:10:31 <lennyb> I am thinking about automatic compare between my CI and the others per commit
15:11:05 <anteaya> the readme doesn't mention a REST api for ciwatch: http://git.openstack.org/cgit/openstack-infra/ciwatch/tree/README.rst
15:11:25 <lennyb> 1x0
15:11:33 <anteaya> lennyb: well gerrit supports a REST query
15:11:42 <mmedvede> anteaya: to answer your question about zuul version, I actually checked out to latest, but did not have chance to restart it, so might see the same regression eantyshev sees
15:11:54 <anteaya> and I'm guessing that ciwatch uses gerrit's REST api for its data
15:12:09 <anteaya> mmedvede: ah okay thanks, now you are prepared :)
15:12:22 <lennyb> anteaya: thanks.
15:12:26 <anteaya> welcome
15:12:39 <anteaya> but I do encourage you to continue to contribute to ciwatch
15:12:52 <anteaya> as I'm sure others using the tool have the same question as yourself
15:13:13 <eantyshev> mmedvede: could you please share the list of future improvements in ciwatch?
15:13:30 <mmedvede> anteaya: ciwatch is only using gerrit event stream to populate its database, not using gerrit API
15:13:37 <mmedvede> (yet)
15:14:13 <anteaya> ah
15:14:36 <anteaya> any thoughts to use the gerrit API?
15:14:48 <anteaya> has there been any discussion around that?
15:15:43 <mmedvede> #link ciwatch bug tracking https://bugs.launchpad.net/ciwatch
15:16:01 <mmedvede> #ling ciwatch blueprtints https://blueprints.launchpad.net/ciwatch
15:16:08 <mmedvede> #link ciwatch blueprtints https://blueprints.launchpad.net/ciwatch
15:16:29 <eantyshev> mmedvede: thanks!
15:16:32 <mmedvede> eantyshev: ^ some of the plans
15:16:36 <anteaya> thank you
15:16:56 <anteaya> #link ciwatch spec to use the REST api: https://blueprints.launchpad.net/ciwatch/+spec/rest
15:17:17 <anteaya> any more discussion around ciwatch?
15:17:54 <anteaya> does anyone have anything else they would like to discuss today?
15:18:02 <mmedvede> anteaya: that link above could be confusing, it is not to use gerrit REST :)
15:18:13 <anteaya> oh okay yes I was confused
15:18:15 <mmedvede> but to implement ciwatch's rest
15:18:28 <mmedvede> need better description
15:18:32 <anteaya> ah thank you for the clarification there
15:19:03 <anteaya> so to answer my own question, there hasn't been any discussion to use the gerrit REST api to get data for ciwatch
15:19:10 <anteaya> correct?
15:20:08 <anteaya> I'm fine if that is the case, just trying to keep up with status
15:20:51 <anteaya> more here or shall we move on?
15:21:07 <mmedvede> anteaya: there was. iirc, we thought it might be good to use REST api to complement data acquired from event stream - I need to check irc logs. But at the moment it would complicate codebase too much
15:21:24 <anteaya> mmedvede: okay thanks, fair enough
15:21:34 <anteaya> okay to move onto next topic?
15:21:41 <mmedvede> yes
15:21:46 <anteaya> thanks
15:21:59 <anteaya> does anyone have anything else they would like to discuss today?
15:22:22 <lennyb> nope.
15:22:28 <anteaya> thanks lennyb
15:22:39 <anteaya> any objections to me closing the meeting?
15:23:10 <anteaya> thanks all for your kind attendance and participation today
15:23:22 <anteaya> I hope you all enjoy the rest of the day/evening
15:23:27 <anteaya> see you all next week
15:23:28 <lennyb> u2
15:23:31 <anteaya> #endmeeting