Security release & Jenkins update on August 15th

[rvagg]

@nodejs/collaborators we're going to have to block off access to ci.nodejs.org to a limited group for testing in preparation for the security releases some time on the 14th UTC so we can run embargoed commits through CI. There is also a Jenkins update due out on the 15th, the day of our release, so I'll be queuing up a Jenkins update after the releases go out before we open it all back up again. Hopefully it'll all be done before the 16th hits us! Will update in this issue when it's all wrapped up and we're back to normal.

[benjamingr]

Thanks for taking care of this and for the update! The hard work of the build team in dealing with security releases is much appreciated.

[maclover7]

Access should now be disabled for nodejs/collaborators on the public CI

[Trott]

Is CI still locked? Should this be closed?

[richardlau]

Yes, the CI is still locked.

[refack]

1. For those who are wondering how come some PRs got CI tests during this lockdown. For several teams who facilitate these security releases (@nodejs/releasers and @nodejs/build), access was kept.

2. As a result of the openSSL upgrade in our infrastructure, CI will fail for existing PRs until they are rebased (or tested with rebasing) - ansible: upgrade to OpenSSL 1.1.0i & 1.0.2p in sharedlibs #1451

3. CI should be back to normal very soon.

[rvagg]

OK, all done, Jenkins upgraded while we had it locked too, there was a security release there too.

@nodejs/collaborators ci.nodejs.org is back and ready to take your jobs.