Repository navigation
Build WG Meeting Sep 12 @ 10 PM UTC #875
Description
When
Sep 12, 2017 10 PM UTC - time in your timezone
Where
- Hangouts on Air, for participants
- Youtube stream, for viewers
- Events page
- Minutes document
- Previous meeting
Agenda
Extracted from wg-agenda issues and pull requests from this repo.
- Demo KeyBox at next WG Meeting #806
- ansible: use gcc 4.9 on CentOS 6 #809
- ansible: use gcc 4.9 on Ubuntu 14.04 #797
- Store resources for Ansible on jenkins ci master #871
All welcome of course, primarily @nodejs/build focused but we're happy to expand.
Please 👍 if you can make the meeting, and 👎 if you cannot.
Activity
joaocgreis commentedon Sep 11, 2017
I won't be able to make it to this one.
I added #809 and #797 to the agenda, and they should be discussed even without me (I added because I can't take them further). I helped with the Ansible changes without realizing that we may not be able to land it because of compatibility (@seishun I'm sorry for this and thanks for all the hard work you've done on those PRs). If I understand correctly, the changes proposed will break 32-bit build on Linux. I don't think this is something we can do for current versions, but don't know if we can for upcoming versions or at all. This needs someone with more Linux experience to weight in.
seishun commentedon Sep 12, 2017
@mhdawson Is it 6AM or 6PM?
@joaocgreis As far as I can tell, #797 doesn't break anything. #809 is "breaking" in the sense that it's not (easily?) possible to install a supported version of gcc on 32-bit CentOS 6, which means it would probably need to be dropped from CI. According to @rvagg (#797 (comment)), public releases are built on CentOS 6, so 32-bit releases would need to be built on a different machine or dropped altogether.
If these changes cannot land, then I'd like to see an alternative suggestion. Leaving it as-is isn't really an option since the CI machines in question (and many others that I haven't looked into yet) currently use unsupported compiler versions. (see #762)
gdams commentedon Sep 12, 2017
@seishun it's at 6PM
piccoloaiutante commentedon Sep 12, 2017
I won't be albe to make it. I haven't done anything in the past three weeks since I've been mostly on vacation.
Trott commentedon Sep 12, 2017
Super minor nit, but this will be at 6PM EDT, not EST, right? If so, I guess the title should be edited to change that... (perhaps even better, just update it to be UTC?)
[-]Build WG Meeting Sep 12 @ 6EST[/-][+]Build WG Meeting Sep 12 @ 10 UTC[/+][-]Build WG Meeting Sep 12 @ 10 UTC[/-][+]Build WG Meeting Sep 12 @ 10 PM UTC[/+]mhdawson commentedon Sep 12, 2017
link for participants https://hangouts.google.com/hangouts/_/ytl/AcMmruOezHj1vtB6EdFoQ4SvUMyS5otpKJAIVcqjiqc=?eid=100598160817214911030
rvagg commentedon Sep 12, 2017
Thanks so much for the Keybox demo @gdams, that's actually pretty exciting! @jbergstroem you should review the video for this.
rvagg commentedon Sep 12, 2017
oh, and @joaocgreis there's some discussion about Windows & 32-bit binaries in there that'll end up in an issue but you may want to listen to the discussion if you have time
dot: add meeting minutes for 2017-09-13
dot: add meeting minutes for 2017-09-13
dot: add meeting minutes for 2017-09-13
dot: add meeting minutes for 2017-09-13
doc: add meeting minutes for 2017-09-13
doc: add meeting minutes for 2017-09-13
doc: add meeting minutes for 2017-09-13
doc: add meeting minutes for 2017-09-13
doc: add meeting minutes for 2017-09-13 (#881)
skavanagh commentedon Oct 24, 2017
@gdams - so I somehow stumbled across this post..
An alternative is to set things up so users can login and set their own keys to the systems under the profiles they have been assigned (and you can then disable those keys anytime). That way you aren't adding the public keys for them.
Loophole-LLC/Bastillion#138 (comment)
This way everyone handles their own keys to discourage sharing / reuse. And if you have keybox generate the key for the users, you can require them to set a good passphrase for the private (at least initially, I guess they could always remove it).
What's nice about setting it up this way.. is it makes it easy to rotate keys, since (after the key has been disabled) the user can just login to keybox and issue new ones for themselves.
Hope this helps!