PAGE
Using MacOS Sequoia (15) and Tahoe (26) Templates
In “Featured” templates, we propose these templates:
CI-MacOS-Tahoe-26.5.1_xcode_gitlab-runnerCI-MacOS-Sequoia-15.0.1_xcode_gitlab-runner
In “Community” templates, you can also find these one:
CI-MacOS-Ventura-13.7_xcode_gitlab-runnerCI-MacOS-Sonoma-14.7_xcode_gitlab-runner
These templates are made available to users with some limitations that you have to consider.
Starting VM
The virtual machine (VM) may be long to start. If it is the case, it’s because the storage volume needs to be prepared.
You have to wait a bit. When the volume in “Allocated” state enters in “Ready” state, the VM will start.
Accessing graphical interface via cloudstack
If you want to use console on CloudStack for accessing to graphical interface of your VM, you will not be able to use keyboard and mouse. The reason is that CloudStack creates VMs with USB 2.0 controllers instead of USB 3.0 controllers.
To connect to your VM in a graphical way, you can use SSH connection combined with a VNC client. Refer to this section for more details.
Warning
For “Tahoe” template, if you change the default password for the user “ci”, you need to connect to the VM by SSH and execute the following command.
sudo sysadminctl -autologin set -userName ci -adminUser ci -adminPassword <your new password>
The autologin configuration is necessary for the connection to graphical interface via VNC.
Using gitlab-runner
Gitlab-runners are already installed to be run in user-mode as required by macOS.
You have just to configure the gitlab-runner client to authenticate to your gitlab project using the gitlab-runner register command.
Here are the limitations on macOS.
Because the service runs only when the user is logged in, you may enable auto-login on your macOS machine to keep the gitlab-runner always running.
For that, the steps are:
- Connect to the VM in a graphical way.
- Log in
- Enable auto-login or disable screen lock using this command:
sudo sysadminctl -screenLock off -password -and enter the user password.