release-macstadium-macos10.10-x64-1 - Unblock 8.12 release

[mhdawson]

As a heads up:

• There are issues with the existing 10.10 osx machine which are blocking the release today
• Normally we would want to add a machine and test on nightlies, but we are starting to add a 10.10 machine to MacStadium as a backup.

This issue is to track/make that visible

[mhdawson]

Manual steps here: #1393

[mhdawson]

Transferred 2 of the required packages to our stable storage on the ci

downloads@infra-digitalocean-ubuntu14-x64-1:~/www/osx$ ls
Packages.dmg XZ.pkg

[gdams]

added host: #1487

[gdams]

following the steps here:

For release machines:

• Install Packages from http://s.sudre.free.fr/Software/Packages/about.html
• Install xz utilities from http://macpkg.sourceforge.net/
• Install Node.js Foundation code signing and package signing certificates
  Available from either the secrets repository under "release" as a passwordless .p12 file
  OS X 10.10: In Keychain Access, "Import Items" and add both the Installer and Application certificates to the "System" (not "login" which is default)
  OS X 10.10: Find the private key for Node.js Foundation under System in Keychain Access, "Get Info" for it, switch to "Access Control" and allow access by all applications. This step requires a physical keyboard under El Capitan and onward.
  Command line alternative (all OS X?): sudo security import /path/to/id.p12 -k /Library/Keychains/System.keychain -T /usr/bin/codesign -T /usr/bin/productsign
  Check with security find-identity -v -p codesigning
• remove test key and replace with release ssh key
• Add ssh_config as /Users/iojs/.ssh/config
• Install the staging key as /Users/iojs/.ssh/id_rsa

[mhdawson]

We have created a new machine but I've tagged it so it won't be used by the regular release job since we first need to validate if PackageMaker is needed for 6.x or not. We should also do some testing with nightly releases first.

I have created a new job called " iojs+release-new-osx-temp" that I think I have configured to use the new machine properly.

Running a test build here to see if it builds/publishes ok: https://ci-release.nodejs.org/computer/release-macstadium-macos10.10-x64-1/

If we decide to publish the release with the new machine we should then be able to use this job to run/create the required artifacts.

[mhdawson]

Looks like the job passed @MylesBorins FYI. In the worst case we should have a machine/job we can use for osx for 8.x. Would be good to get some additional testing though...

[mhdawson]

Job to test if we can properly build a 6.x release without PackageMaker: https://ci-release.nodejs.org/job/iojs+release-new-osx-temp/2/

[rvagg]

👍 looking good, I also confirmed in Makefile that we removed the PackageMaker dependency prior to Node 6, so we can expunge that entirely from our records 🎉.
Once we get this online I'd love to get the release machine off my network, maybe the test one too. I could keep them around for backup purposes but maintaining these VMs isn't fun on macOS.

[mhdawson]

Test job for 6.x also passed.

@nodejs/build what other testing should we do before switching over to the new machine?

[mhdawson]

@nodejs/build, ping. We might want to \switch over after the 8.12 tomorrow release so that we get a few current releases before the 10.X goes LTS. @MylesBorins any suggestions/concerns over timing for a switch over?

[joaocgreis]

@mhdawson for Windows machines I build a test release, and make sure it can be installed and native modules can be compiled with/for it. Make sure the package is signed (ref nodejs/node#14179, though there's not much of a conclusion there). Not sure if there's anything else specific for osx, but if the items above work it should be ok to add to the pool. I'd keep both around for a few days, since the old one is working now.

[MylesBorins]

+1 on the plan

…

On Mon, Sep 10, 2018, 7:27 PM João Reis ***@***.***> wrote: @mhdawson <https://github.com/mhdawson> for Windows machines I build a test release, and make sure it can be installed and native modules can be compiled with/for it. Make sure the package is signed (ref nodejs/node#14179 <nodejs/node#14179>, though there's not much of a conclusion there). Not sure if there's anything else specific for osx, but if the items above work it should be ok to add to the pool. I'd keep both around for a few days, since the old one is working now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1486 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV_tPUGwYpnX18NwXEu2o2xNJa64cks5uZvVtgaJpZM4WZuJi> .

[mhdawson]

@gdams could you take the action to complete the steps that @joaocgreis suggests. I think Rod may have validated some of those, but a complete check makes sense. Earlier test build was here: k: https://ci-release.nodejs.org/computer/release-macstadium-macos10.10-x64-1/, and one for 6.x here. We probably also want to test 10.x: kicking off build https://ci-release.nodejs.org/job/iojs+release-new-osx-temp/3/

Let me know if you need me to kick off any other builds or need help mapping the builds to test releases published on the Node.js web site.