Build WG Meeting 2016-02-23

[orangemocha]

Meeting Time: 8PM Tuesday February 23rd UTC, or in your local timezone:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Build+WG+Meeting&iso=20160223T20&p1=%3A

Where

• For participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYeJy9oYOhRWJ3Ne5lQ8Cl2wHdHTRngWx23UVeaMUJGWRNxUOA?hl=en&authuser=0
• For viewers: http://www.youtube.com/watch?v=I_RHZVFPwMU

Agenda

Extracted from wg-agenda issues and pull requests from this repo.

• New experimental stress test job / Access permission [https://github.com/New experimental stress test job / Access permission #331]
• Setup to publish benchmark results to nodejs.org [https://github.com/Setup to publish benchmark results to nodejs.org #281]
• [Rod] Backups for our resources: what's the status here, what can we do to move forward or is it done?

If there are any items that you would like to discuss at the meeting, please tag new or existing issues with the wg-agenda label, or simply post them in a comment here.

All welcome of course, primarily @nodejs/build focused but we're happy to expand.

[orangemocha]

Meeting is confirmed for tomorrow. Please take the time to tag any issues that you would like to discuss. Thanks!

[rvagg]

I'm not sure I actually want to get up early tomorrow, I may do but just in case I don't, here's some thoughts on issues:

• Jenkins access:
  • I'd like to make it easier for additional people to use Jenkins, in general
  • I am concerned about further encouraging a lax attitude towards Jenkins use even by Collaborators. I don't think we've done a good job at reinforcing how important it is to check code before throwing it at Jenkins, mostly because it feels like an isolated system and looks like Travis et. al. but that's not the case and we have to ensure that everyone pushing code at Jenkins takes responsibility for doing so, knowing that they could be exposing our CI system to malicious code that has greater impact beyond individual runs. Perhaps we need to put some thought into this, a checkbox maybe that they have to tick to acknowledge the risks?
  • We need to switch to the per-project authentication mode where we can assign different permission levels to different GitHub groups, this will make this process much easier and I'd be much more comfortable handing out access.
  • We do a lot of hardware sharing so even a per-group restriction doesn't go far enough. For example, the smoke testing reuses CI machines. Do we need to be more rigid in our separation of servers?
• Running V8 test suite: does this need to be on the agenda, is something blocking that a meeting is required for?
• Publish benchmark results: yes, I'm guessing I'm the blocker here, sorry, there's no reason I should be a blocker as others have access to nodejs.org it's just that I express the strongest opinions about things done on there I suppose. I'm happy for someone else to propose the technical steps to getting this done, allowing review and then making it happen. Otherwise it can wait for me to get to it (I may have to be reminded again!). I'm working my way through a big backlog at the moment, I've let things slip over the past ~week so am quite behind.
• Backups for our resources: what's the status here, what can we do to move forward or is it done?

[mhdawson]

At this point I don't think "Running V8 test suite"needs to be on the agenda, in past meetings it was left there simply so I could give build team members an update. I'm slowly working through the issues/questions that need to be resolved in order to get regular runs.

[orangemocha]

Ok, I removed "Option to run V8 test suite [#199]" from the agenda.

I think the conversation about Jenkins access should be had off the air, given the security sensitivity.

[jbergstroem]

Regarding backups: The plan was to get it in last week but when the jenkins security notice came up I decided to push this forward until it's settled and we have a 'known state' again.

[orangemocha]

The private discussion ended taking a large portion of the hour, so we decided not to start the broadcast.

Meeting notes are here: https://docs.google.com/document/d/1srGblqnYaC5k-lHCSy08ar4aiq02lV2zWPA4vtzp5KQ/edit?usp=sharing