[devel at bb.net] Weekly Meeting Notes

Tue Dec 19 17:42:48 UTC 2017

Meetbot was broken today, so no minutes, sorry :(

Here is the log of the meeting:

12:00:10 <•djmitche> #startmeeting weekly
12:00:17 — •djmitche waves to adoring
crowd

12:00:22 <•djmitche> #topic Introduction
12:00:46 <•djmitche> http://bit.ly/2rup31x
12:01:28 <rjarry> o/
12:01:39 <•djmitche> Who's here?
12:01:40 <rjarry> <-- here
12:02:43 <•djmitche> #topic Week In Review
12:03:04 <•djmitche> tardyp: ^^
12:03:25 <•tardyp> hi
12:03:51 <•djmitche> looks like a slow week, based on the email?
12:04:07 <•tardyp> This week. We had some patches for badge plugin
12:04:24 <•tardyp> which is good popularity test
12:04:29 <•bdbaddog> Greetings!
12:04:43 <•djmitche> #info Badges work landing this week
12:04:44 <•djmitche> https://github.com/buildbot/buildbot/pull/3833
12:04:47 <•djmitche> https://github.com/buildbot/buildbot/pull/3832
12:05:15 — •djmitche waves to bdbaddog
12:05:23 <•tardyp> Then we have some work on going with reworking the
github services to have a common accessor
12:05:42 <•djmitche> can you say more about that?
12:06:34 <•tardyp> https://github.com/buildbot/buildbot/pull/3827
GitHubApiService is a common accessor for all Github
12:07:01 <•tardyp> allow to communalise authentication stuff
12:07:11 <•djmitche> I see, a single way of accessing the GH API from
various components
12:07:17 <•tardyp> yes
12:07:21 <•djmitche> very cool
12:07:28 <•djmitche> any updates on releases?
12:07:52 <•tardyp> no new release for now. We still have some outtanding
bugs in 0.9.14 UI
12:07:56 <•djmitche> #info GitHubApiService as a common way of accessing
Github APIs from everywhere
12:07:59 <•djmitche> ok
12:08:13 <•djmitche> #topic Revisit MOSS Completion
12:08:18 <•djmitche> bdbaddog: ^^ is this you?
12:09:44 <•djmitche> m
12:09:50 <•bdbaddog> yes. I think the intent was to mark the outstanding
moss bounty for better handling of ec2 latent workers as resolve by work
done by tardyp and contribute the bounty to the project?12:09:57
<•bdbaddog> Does that sound right?
12:10:18 <•djmitche> that was my understanding too
12:10:39 <•djmitche> do we need to formalize that somehow?
12:10:41 <•tardyp> yes
12:10:42 <•bdbaddog> also I'll need to write an end-of-award report.
12:10:57 <•bdbaddog> I'll contact Gerv and see what needs to be done for
bounty #2.
12:11:18 <•tardyp> I dont remember what was bounty 2
12:11:35 <•djmitche> it was generally about making EC2 latent workers
better.. I don't recall details
12:11:38 <•djmitche> either
12:11:46 <•bdbaddog> http://trac.buildbot.net/ticket/3392
12:12:08 <•bdbaddog> are the 4 bullets in the ticket resolved?
12:12:16 <•tardyp> then what was bounty 1
12:12:31 <•bdbaddog> bounty 1 was slave->worker
12:12:47 <•bdbaddog> $10k, bouty 2 is $5k
12:13:10 <•tardyp> ah yes
12:13:48 <•tardyp> So actually what was done is not really about EC2
worker, but is more about the latentworkers in general
12:15:09 <•djmitche> yeah, the needs of the project drifted a bit
12:15:20 <•tardyp> basically, you can replace EC2 by "hyper.sh" and this is
actually what we run in nine.bb.net
12:15:29 <•djmitche> ah, that's good angle
12:15:36 <•tardyp> we don't loss any hyper.sh container
12:15:49 <•bdbaddog> what about ec2? is that affected by any of the fixes?
12:15:53 <•djmitche> so over time the needs changed, but the underlying
issue of reliability and support for latent workers was implemented
massively as hyper.sh
12:16:30 <•tardyp> the fixes implemented for hyper.sh were actually in the
core latent worker, and thus applicable for ec2.
12:16:49 <•tardyp> even if technically, I didn't invest the money to battle
test ec2
12:17:03 <•tardyp> I know that there are people using ec2 latent worker
though
12:17:05 <•bdbaddog> oh I guess migrated to:
https://github.com/buildbot/buildbot/issues/2961
12:17:14 <•tardyp> and we don't have outstanding ec2 bugs afaik
12:17:34 <•bdbaddog> is there documentation on how to run latent slaves and
specificaly ec2?
12:17:40 <•bdbaddog> of if not, then hyper.sh ?
12:18:20 <•tardyp>
http://docs.buildbot.net/latest/manual/cfg-workers-ec2.html
12:18:44 <•tardyp> I think it is pretty comprehensive
12:18:52 <•bdbaddog> o.k. I'd mark that bullet as complete.
12:18:53 <•tardyp> however I don't know if it is up-to-date
12:19:05 <•bdbaddog> the shutting down the instance bullet?
12:20:55 <•tardyp> yes, the master is properly stopping the latent worker
now when build are stopped
12:21:13 <•tardyp> even when master crash it will stop the latent worker at
restart
12:22:04 <•bdbaddog> what happens if the master crashes? would an ec2 work
remain running indefinitely?
12:22:28 <•djmitche> (should we continue this or hit the other topics
before :30 past?)
12:22:41 <•bdbaddog> move to mailing list? botherders or regular?
12:22:50 <•djmitche> probably botherders
12:23:05 <•bdbaddog> k. next topic then?
12:23:06 <•tardyp> ok
12:23:16 <•djmitche> #topic New SVG Icon for 1.0
12:23:23 <•djmitche> any new feedback here?
12:23:33 <rjarry> I am still leaning towards the blue version :D
12:24:47 <•tardyp> rjarry: can you advocate your position on the issue?
12:24:58 <rjarry> crap I forgot to do that !!
12:25:10 <rjarry> I'll add a reminder, I wont have time tonight
12:25:16 <•djmitche> ok :)
12:25:22 <•djmitche> #topic Debian support
12:25:28 <•djmitche> any news?
12:25:30 <rjarry> yes
12:25:44 <rjarry> I submitted to be maintainer of buildbot packages
12:26:09 <rjarry> after some discussions with Mathias Klose, we will
maintain a single source package (in debian terms)
12:26:23 <•djmitche> #info rjarry will be maintainer for a single source
package
12:26:31 <rjarry> --> no systemd integration to avoid pissing Kfreebsd guys
off
12:26:55 <•djmitche> haah
12:27:11 <rjarry> --> no building from pypi archives (those with .js
precompiled), this goes against debian policy
12:27:24 <•djmitche> that makes sense
12:27:42 <•djmitche> but those can get pulled directly into a webpack,
rather than depending on 10000 other debian packages?
12:27:47 <rjarry> this means we can update buildbot and buildbot-worker,
but not the www* pacakges
12:28:00 <rjarry> yeah
12:28:08 <•djmitche> ok
12:28:12 <•djmitche> sounds complicated, but workable :)
12:28:16 <rjarry> I guess having the www* packages in debian willr require
some work
12:28:21 <rjarry> upstream work, i mean
12:28:24 <•djmitche> yeah
12:28:40 <•djmitche> anything else?
12:28:46 <•djmitche> chapter progress update is quick...
12:28:47 <rjarry> decaffeinate, and find a lighter build system
12:28:58 <•djmitche> decaf, yuck
12:29:01 <•djmitche> ;)
12:29:06 <•djmitche> #topic Chapter Progress
12:29:12 <rjarry> btw: even webpack has a lot of deps that are not
integrated into debian yet
12:29:28 <•djmitche> #info Incorporating updates from reviews, then will
ask Apress for review later this week
12:29:42 <•djmitche> hm
12:29:46 <•djmitche> webpack is pretty awesome though
12:29:54 <rjarry> yup
12:30:00 <•djmitche> any other business?
12:30:09 <rjarry> work in progress:
https://wiki.debian.org/Javascript/Nodejs/Tasks/webpack
12:30:27 <•djmitche> oh cool!
12:30:34 <•tardyp> ah I though webpack was done..
12:30:43 <rjarry> tardyp: can we merge this ?
https://github.com/buildbot/buildbot/pull/3815
12:31:05 <•tardyp> there is also
https://wiki.debian.org/Javascript/Nodejs/Tasks/guanlecoja
12:31:07 <•djmitche> that looks like a typical npm dep tree :)
12:31:12 <•djmitche> #endmeeting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20171219/664ca574/attachment.html>