We are excited to announce that we released a new generation of macOS on December 15th!! These new resources can speed up your builds by up to 50%! Gen2 macOS resources is available to all customers on a Performance, Custom, or Scale plan. We are only offering a medium size option with these resources at this time.
As part of this release, we are also introducing new resource class naming, in an effort to provide more clarity on the executor being used. Note: this change will not impact our existing medium and large macOS resource classes.
If you want to start running your macOS jobs on the next generation resources, just update your config to the macos.x86.medium.gen2 resource class!
jobs: # a basic unit of work in a run
build-and-test: # your job name
xcode: 12.5.1 # indicate your selected version of Xcode
resource_class: macos.x86.medium.gen2 # new generation resources
steps: # a series of commands to run
- checkout # pull down code from your VCS
- run: bundle install
command: bundle exec fastlane $FASTLANE_LANE
Quick update: We’re investigating an issue that impacts our Gen2 macOS resources and, unfortunately, need to delay this launch. I’ll post another update once I have a new release date, but expect it will be next week, if not sooner. Thank you for your patience and understanding!
@brow is correct! You will be defaulted to the medium resource class until the new class becomes available.
You may see a message about upgrading to a Performance plan when this occurs, but you can disregard that. We’re also looking into updating the message to avoid confusion. Thanks, again, for your patience!
We have identified the root cause of the issue and are now working on a solution. I don’t have a new release date, yet, but should be able to provide one by the end of the week!
We have also fixed our message to reduce confusion for those who try to use this new resource class before they’re available. Additionally, customers who were part of the closed preview should continue using the old resource class tag until the new launch date.
Just tested this and it looks like it does perform a lot faster! However, we have a highly parallelized workflow and we are seeing most workers take three minutes to get allocated a VM. Is this expected and will it improve in the future? It takes away from a lot of the speed gain
I’m also seeing very slow environment spin-up times - as slow as 5 minutes today. This really isn’t acceptable when we’re already trying everything we can to keep our build times as quick as possible. A 5 minute spin-up time can multiply quickly when you have 5 or 6 jobs in your workflow.
I’m seeing this on both the stable Xcode 13.2 images and the new MacOS 12/Xcode 13.3 beta images.
Although the nature of using Mac environments means that spin-up times can vary 5 minute spin-up times are unexpected. Did you experience this before today? Would you mind if I messaged you privately and you can send me a link to the build where you were experiencing the slow spin up times and we can investigate it on our end?