Deploy macOS 10.14 Jenkins agents
#4 Updated by Davide Pesavento 3 months ago
Junxiao Shi wrote:
I notice that macOS 10.12 and macOS 10.13 slaves were incorrectly labelled as "OSX". The name "OSX" is no longer used after OSX 10.11.
Nobody cares that Apple changed the marketing name of their operating system. We use "OSX" in the
NODE_LABELS config variable and I see no good reason to change that, it would be a waste of time and effort. Even Travis still uses "osx" and "osx_image" in the configuration file. I'm against changing anything in this regard, let's spend our energy in a more productive way.
Be sure not to repeat the same mistake this time.
Please use a different tone when expressing your personal opinion.
#6 Updated by Junxiao Shi 3 months ago
I don't know the deployment and maintenance procedure. How much different or difficult is it compared to other agents?
The easiest for this and all future macOS deployment would be using a cloud service.
It's not cheap, but saved labor and reduced developer frustration can more than justify the cost.
#8 Updated by Junxiao Shi 3 months ago
monaco has 4GB of RAM so it can fit only one VM. You still should use a VM (and not build on physical machine) to ensure easy recovery.
To get full redundancy: place one set of macOS 10.12-10.14 among
mavericks, and place another set at CSU. Any one node failure would not take out all slaves for an OS.
#11 Updated by Md Ashiqur Rahman 3 months ago
I'm getting the following error trying to get Alex's 10.13 box:
The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it. If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is released. Name: ndn-jenkins/osx-10.13 Address: https://vagrantcloud.com/ndn-jenkins/osx-10.13 Requested provider: [:virtualbox]