19:00:47 #startmeeting ci 19:00:48 Meeting started Tue Aug 28 19:00:47 2012 UTC. The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:50 The meeting name has been set to 'ci' 19:01:31 so, i think we've talked about most of the current projects on the ML... 19:01:54 clarkb is working on some issues with the SCP plugin that copies logs to the log server 19:01:56 * LinuxJedi should really read that this week 19:02:29 when we're satisfied with that, we'll cut back on the build history that jenkins keeps 19:02:34 which should hopefully speed things up. 19:02:52 ++ 19:03:15 as part of that work I have also gotten the nosetests html output to include skipped tests 19:03:43 i'm working on getting the jobs to use the refs that zuul is composing, which should make gerrit-git-prep simpler, and actually allow us to switch to cherry-pick mode if needed. 19:04:17 though it looks like there's a bug in zuul that i need to look at first 19:04:36 (related to dequeuing failed changes) 19:05:15 after that, i'd like to do some work to enable us to run multiple jenkins masters... 19:05:29 i think dividing the load will help some.... 19:05:51 jeblair: is that something zuul would need to be aware of? 19:05:53 part of our problems, i think, stem from having so many slaves; this should cut down on the number of threads in use. 19:05:57 clarkb: yep 19:06:10 clarkb: and maybe the jenkins job builder too. 19:06:31 * LinuxJedi is looking forward to the multiple masters 19:06:41 should make things easier to find :) 19:06:50 i'm thinking that zuul should use gearman to dispatch jobs, and then there should be a little zuul agent on each master that handles interacting with jenkins. 19:07:41 so a project goes to a random jenkins rather than a jenkins per-project? 19:08:02 run goes to a random jenkins even 19:08:32 maybe, or, i've been thinking we could try having an oneiric, precise, and devstack jenkins... so split them up by node type 19:09:33 but i think the general approach should be flexible, so we can split up the jenkinses however we need 19:10:17 (side effect, this will tie zuul to jenkins slightly less -- things other than jenkins could join the gearman system) 19:11:14 we also have some new zuul features -- the non-voting tests we talked about last week are live, and running for nova pylint 19:11:27 and i'm testing out running coverage that way too 19:12:07 fungi has joined us 19:12:12 welcome fungi! 19:12:17 thanks! 19:12:48 fungi is looking into the trivial-rebase hook 19:12:54 a long requested feature. 19:13:05 yeah, claimed on lp and mostly working on my dev vm 19:13:21 awesome! 19:13:29 also mawagon1 and dkehn have joined us 19:13:29 my lack of prior exposure is biting me there, so i'm brushing up on gerrit hooks at the moment 19:13:57 fungi: i think you'll become a gerrit expert fast with this one. :) 19:14:06 looks trivial enough 19:14:12 heh 19:14:16 ;) 19:15:56 anyone else have things they're working on they'd like to talk about? 19:16:26 i ran into a handful of things so far 19:16:31 http://wiki.openstack.org/Meetings/CITeamMeeting 19:16:41 i assume that's not updated regularly any longer? 19:16:51 or is there a more proper home for it? 19:17:39 nope, our normal chair does not regularly update it. 19:17:59 at least partially in response to that (there ore some others with similar habits), i updated meetbot to require a meeting nam 19:18:11 that works 19:18:15 and a name 19:18:19 name, so future meetings will be findable in the directory structure 19:18:29 on eavesdrop.openstack.org 19:18:32 #link http://eavesdrop.openstack.org/meetings/ 19:19:02 this one is already in progress. :) http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-08-28-19.00.log.txt 19:19:15 another trivial item... the gerrit initscript. should we add lsb headers, do you think? 19:20:17 fungi: that might be a good patch for upstream gerrit 19:20:25 i would assume so 19:20:32 good point 19:20:44 i'll try to get a patch to them when i get a moment 19:21:09 I think mtaylor may need to do something with their CLA 19:21:36 seems like he had to add me after I got an account on their gerrit server 19:21:55 yep, but that's an hp-specific thing we don't need to talk about in the openstack meeting. :) 19:22:09 nevermind then 19:22:37 fungi: what else ya got? 19:22:50 on a similar gerrit note, the instructions on the ci site assume debian (ubuntu) package management, but then use useradd instead of adduser 19:23:05 maybe just a personal nitpick 19:23:09 fungi: we'll probably just drop that since it's all managed by puppet now 19:23:35 point taken 19:23:38 fungi: one is an alias of the other 19:23:57 fungi: in the long run, we don't need installation instructions we don't use. that was how it was initially set up before we puppetized everything. 19:24:01 really? thought adduser was a wrapper with different semantics 19:24:21 jeblair: makes sense 19:25:17 anyway, that's all i have so far 19:25:22 #topic open discussion 19:25:29 (as if it hasn't been) 19:25:39 anyone else? 19:26:27 MRaaS has been re-added to Stackforge 19:26:34 that is about all I remember 19:27:06 LinuxJedi: cool; you brought the jobs up to current standards, right? 19:27:22 LinuxJedi: and are they committing yet? 19:27:43 jeblair: well 'job' only the merge one for now. I haven't seen them committing yet, I have been teaching them how git/gerrit/everything works... 19:28:04 jeblair: it is a Java project so we have to figure out how to test that at some point 19:28:59 lovely 19:29:35 oh, keystone has a feature branch 19:29:46 so there is now a feature/keystone-v3 branch in gerrit 19:30:12 we're experimenting with letting the keystone-drivers group land merge commits there, to keep it going as a long running feature branch 19:30:28 that will eventually merge into master, some time during grizzly i expect 19:30:47 they are pushing directly to the branch? 19:31:01 no, it's still code reviewed in gerrit 19:31:19 the difference is that group has an acl that lets them upload a merge commit 19:31:38 #link http://wiki.openstack.org/GerritJenkinsGithub#Merge_Commits 19:31:46 there's the preliminary documentation on that. 19:32:09 this is something we discussed a bit at the last summit, but this is the first time it's been requested 19:32:13 so it's still pretty experimental. 19:32:47 but because of the way we write all of the jenkins jobs, etc, it shouldn't require any extra support. 19:34:51 anything else? 19:38:12 i reckon that's it then, thanks! 19:38:14 #endmeeting