![]() ![]() I also created a ~/.ruby-version file with ruby 2.6 specified. To do this, I had to enable the chruby autoswitcher, by changing the default shell to be bash -login. To work around this, I changed the default Ruby to be 2.6. This left our customers unable to install gems that had native dependencies. Xcode 11 included the macOS 10.15 SDK, which had the system headers for Catalina, including the Ruby 2.6 headers (rather than Ruby 2.3 that shipped with Mojave). When Xcode 11 shipped, things broke for our users.If you changed your shell to bash -login, this would trigger ~/.bash_profile to be run before each step, and auto-switching would work. Since we used a non-login shell by default on all operating systems, this mean that auto-switching didn’t run out of the box. chruby and the auto-switcher were installed, and sourced in ~/.bash_profile. The images prior to Xcode 11 all had the system Ruby as the default image.Our policy with Ruby has been to ship the system Ruby as the default Ruby, and to install the latest stable versions of Ruby as listed on.Here is a short history of the recent Ruby changes for context: I’m trying to find a delicate balance with how much customization to do to macOS when we create the images. You can customize the shell for an executor, job or run command, which will allow you too run a command with zsh, should you wish: jobs: By default, commands on macOS run with /bin/bash -login -eo pipefail -c $COMMAND. You can switch it on yourself should you wish.Ĭatalina ships with zsh as the default shells, but with CircleCI, the default shell is still bash. chruby auto-switching is not enabled by default.chruby is installed, and is on the path, and there are two additional versions of Ruby installed, 2.5.7 and 2.6.5.The system Ruby that comes bundled with 10.15 is 2.6.3.My hope is that upgrading to Catalina will resolve these issues, and using Ruby will be more straight forward. This forced us to make some breaking changes with Ruby. The last few releases of Xcode on CircleCI were problematic for Ruby users, due to issues with how Xcode 11 shipped the macOS SDK. The manifest of installed software is here. We used to set the timezone to PDT/PST, which caused some problems each time there was a daylight saving change. The OS has been upgraded to macOS 10.15 (19A602) Catalina.This is the first image that we’ve built with Catalina, so there might be some bugs – please let us know if you find anything out of the ordinary. You can select this image by selecting 11.2.0 as follows: jobs: The new image contains Xcode 11.2, running on Catalina. We have released Xcode 11.2, which will replace the beta release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |