16:31:14 <djmitche> #startmeeting weekly
16:31:14 <bb-supy> Meeting started Tue Jul 12 16:31:14 2016 UTC and is due to finish in 60 minutes.  The chair is djmitche. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:31:14 <bb-supy> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:31:14 <bb-supy> The meeting name has been set to 'weekly'
16:31:30 <djmitche> #topic Introduction
16:31:50 <djmitche> #info Agenda: https://titanpad.com/ep/pad/view/buildbot-agenda/SnMLW2PyWE
16:32:10 <djmitche> how about a roll-call? who's around?
16:32:23 <tomprince> I'm around.
16:32:37 <skelly> here
16:33:32 <djmitche> tardyp: you still around?
16:33:47 <djmitche> rutsky: ?
16:34:17 <tardyp> already 6:30
16:34:31 <tardyp> was messing up with pokemon go :-}
16:34:35 <djmitche> haha
16:34:45 <djmitche> it's taking over the world!
16:34:58 <djmitche> #topic Development Week in Review
16:35:12 <djmitche> looks like a number of small release-related fixes
16:35:34 <djmitche> there's design work for "credentials management"
16:35:36 <tardyp> yes, and a bunch of metabuildbot fixes
16:35:55 <djmitche> yes -- what's the summary of those fixes/
16:35:57 <djmitche> ?
16:36:30 <tardyp> lots of messup of the virtualenvs
16:36:40 <tardyp> actually those one were in the metabbcfg
16:37:06 <djmitche> #info Design work for credentials management (a way to keep credentials used by steps on the master)
16:37:56 <tardyp> some cleanup PR by tomprince about pickles
16:38:08 <djmitche> #info lots of metabuildbot fixes, making virtualenvs work better
16:38:18 <tardyp> and one PR for unimportant triggers
16:38:21 <djmitche> #info removal of leftover pickle-related code by tomprince
16:38:27 <djmitche> what did that mean, unimportant triggers?
16:39:02 <tardyp> in the trigger steps. Some builds can be marked as unimportant, and not taken in account for results
16:39:07 <tardyp> but still waited
16:40:00 <djmitche> #info support for not waiting for builds for unimportant changes
16:40:06 <djmitche> great
16:40:18 <djmitche> no word from rutsky so i assume no update on 2340
16:40:28 <tardyp> no. it s not unimportant changes its unimportant configs
16:40:30 <djmitche> I think I'll remove that from the agenda -- it is substantially done
16:40:37 <djmitche> oh
16:40:38 <djmitche> #undo
16:40:38 <bb-supy> Removing item from minutes: <ircmeeting.items.Info object at 0x8069765d0>
16:40:39 <tardyp> like if we would trigger a build for python3
16:40:50 <tardyp> this one always fail, but we dont account it
16:42:35 <djmitche> ok
16:42:54 <djmitche> #topic 0.9.0rc1 release status
16:43:27 <djmitche> I haven't seen a great deal of feedback yet -- have you?
16:43:52 <djmitche> #info 0.9.0r1 was released July 7
16:44:02 <tardyp> I did not
16:44:04 * tomprince would guess that people interested in using buildbot 0.9 are likely already using it.
16:44:14 <djmitche> agreed
16:44:18 <djmitche> it's also not been long
16:44:22 <tardyp> maybe
16:44:30 <djmitche> hopefully some of the folks using betas will upgrade to rc1 and provide some feedback
16:44:42 <tardyp> so you would advice that we release 0.9.0 without waiting too much?
16:44:49 <djmitche> #info No feedback yet -- hopefully beta users will upgrade and offer feedback
16:45:08 <djmitche> I think if there's no feedback, that's probably a good idea
16:45:31 <djmitche> but if there's feedback, or even people saying "I'm working on deploying it", we could give them time
16:45:54 <tardyp> I have one week of vacation next week. the week after I can fix remaining issue if there are and release..
16:46:28 <djmitche> that'll be good timing
16:46:42 <bb-github> [13buildbot] 15Riziero commented on issue #2315: guys I've got no idea how to fix the docs. Could you give a lead? Thanks :) 02https://git.io/vKWYf
16:46:49 * djmitche skips 0.8.x since sa2ajj isn't here
16:47:04 <djmitche> #topic     docs update failing (http://trac.buildbot.net/ticket/3576 )
16:47:15 <djmitche> did the docs start working again once we unstuck Ansible?
16:47:23 <tardyp> I forgot to look at it
16:47:53 <tardyp> it is not up to date
16:48:03 <tardyp> http://docs.buildbot.net/latest/tutorial/docker.html still has old screenshots
16:48:15 <djmitche> ah, ok, thanks -- i was lacking a way to tell the difference
16:48:49 <bb-trac> [trac] #3576/defect (assigned) updated by dustin (This is still an issue.  http://docs.buildbot.net/latest/tutorial/docker.html still ...) http://trac.buildbot.net/ticket/3576
16:49:15 <djmitche> #action djmitche to look more deeply
16:49:15 <tardyp> why wouldn't we just use http://buildbot.readthedocs.io/en/latest/
16:49:29 <djmitche> we could do that too :)
16:49:32 <tardyp> and just stop docs.bb.net
16:49:36 <djmitche> there was a time *that* didn't update very ewll
16:49:43 <djmitche> well, docs has the historical stuff, and a lot of links point there
16:49:56 <tardyp> yeah
16:49:58 <djmitche> but for latest, yes
16:50:11 <skelly> ansible hasn't been unstuck
16:50:13 <bb-trac> [trac] #3576/defect (assigned) updated by dustin (We can also consider just pointing to readthedocs for latest.) http://trac.buildbot.net/ticket/3576
16:50:15 <skelly> I haven't had time
16:50:34 <djmitche> I deleted its tmp files and whatnot
16:50:35 <bb-github> [13buildbot] 15tardyp commented on issue #2315: You can use "make docschecks" to run locally those tests... 02https://git.io/vKWOW
16:50:37 <djmitche> but maybe i missed something
16:50:48 <djmitche> #topic better handling of EC2 - MOSS - bounty
16:51:02 <djmitche> so I updated http://trac.buildbot.net/ticket/3392
16:51:04 <skelly> yeah, that was one part but there's something else too
16:51:11 <bb-github> [13buildbot] 15tomprince commented on pull request #2314 14a7c0e06: @tardyp I don't think this document is not intended to be included in the docs as-is, but is rather aimed at the developers to get feedback on the idea. Thus responding to specific details of the wording, formatting and organization in the documentation probably isn't relevant at this point. 02https://git.io/vKWOV
16:51:33 <djmitche> to make the bounty project more concrete
16:51:36 <djmitche> and emailed a few people
16:51:44 <djmitche> one replied to indicate he's interested
16:51:51 <tardyp> cool
16:51:56 <djmitche> #info Dustin has updated the bug to be more concrete
16:52:21 <djmitche> #info Please, especially those interested in EC2, broadcast this US$5000 opportunity to your social circles!
16:52:29 <tardyp> FYI I am working on hyper.sh support on buildbot
16:52:37 <djmitche> #topic hyper.sh support
16:52:48 <djmitche> good point -- can you say more about what that will look like?
16:52:55 <tardyp> which also involve properly shuting them down
16:53:16 <tardyp> any improvement I do for hyper will also work for ec2 as this is really abstratlatent stuff
16:53:35 <djmitche> great
16:53:45 <tardyp> it is a latentworker which start workers on the hyper infra
16:53:59 <tardyp> hyper is really just the docker api, with another auth layer
16:54:01 <tomprince> tardyp: Do they not provide the docker api?
16:54:04 <tomprince> Ah.
16:54:15 <tardyp> and some stuff removed
16:54:24 <tardyp> so you cannot really use the same code
16:54:29 <djmitche> #info Hyper.sh is a docker-based cloud hosting environment
16:54:49 <djmitche> #info Pierre is working on an interface to run builds in hyper.sh
16:55:01 <djmitche> and hyper has offered Buildbot some credit to support that?
16:55:06 <tardyp> I'm now at a PoC point lots of hacks but the code is there https://github.com/tardyp/buildbot_travis/tree/hyper
16:55:27 <tardyp> yes they provided 3 years of travis like CI needs
16:55:31 <tardyp> which is about $500
16:56:20 <bb-github> [13buildbot] 15tomprince commented on issue #2314: I think having a story for credential management is a good idea. However, I don't think buildbot should get into the business of managing secrets itself. Rather I think it would make more sense to integrate with existing systems for that (e.g. [Vault](https://www.hashicorp.com/blog/vault.html), [Barbican](https://wiki.openstack.org/wiki/Barbican)) rather than trying to get secure credential storag
16:56:28 <tardyp> this is  not a lot, but they are a smal startup right now
16:56:37 <djmitche> that's great, though
16:56:44 <djmitche> a partnership that helps both sides!
16:56:56 <tardyp> we will see how this partnership will do
16:58:13 <djmitche> hopefully well :)
16:58:16 <djmitche> ok
16:58:16 <tardyp> I will have them by phone tomorrow
16:58:27 <djmitche> cool
16:58:49 <djmitche> #topic Re-visiting Buildbot infrastructure
16:59:01 <djmitche> #info BB infrastructure is still only half-Ansiblized
16:59:09 <djmitche> and it's difficult to test changes
16:59:33 <djmitche> also, Ansible fails a lot -- runs are retried, but even so it leaves zombie processes around
16:59:43 <djmitche> and sometimes gets "stuck" and won't run for weeks
16:59:54 <djmitche> I've got some time coming up during which I will try to address some of these things
17:00:28 <djmitche> probably fixing Ansible with more wrappers
17:00:40 <djmitche> and just barreling ahead into Ansibilizing the remaining jails
17:01:14 <tardyp> cool!
17:01:25 <djmitche> we'll see
17:01:26 <djmitche> any other business?
17:01:36 <djmitche> I'm really psyched to see 0.9.0 come out :)
17:01:43 <tardyp> \o/
17:02:52 <djmitche> #endmeeting