#Parallels 13 mac clone vm for mac#
#Parallels 13 mac clone vm windows 10#

I traced that (last year) and it turns out that the cloning of the VM gives it a new MAC address, and gitlab-runner looks for the old MAC address (of the original VM, not the clone).

#Parallels 13 mac clone vm for mac#

There's a tell-tale error in the gitlab-runner output: ERROR: Job failed (system failure): IP lease not found for MAC address 001C42C13862 in: /Library/Preferences/Parallels/parallels_dhcp_leases duration=6m40.688084247s job=1125551877 project=25368177 runner=xz2gps Just tried a new gitlab-runner setup (with gitlab-runner on the Mac and using Win10 under Parallels) and it doesn't work. Used GitLab Runner version Version: 12.6.0

#Parallels 13 mac clone vm windows 10#

The defined stage should complete! Runner Output Log 1 Running with gitlab-runner 12.6.0 (ac8e767a)Дў on Parallels Windows 10 VM rpMNC3QoДҐ ERROR: Preparation failed: PrlctlOutput error:Д© ERROR: Preparation failed: PrlctlOutput error:ДЎ3 ERROR: Job failed: execution took longer than 1h0m0s seconds From there, the build process will not proceed any further and you'll be left with a Windows 10 VM running happily doing 0. The Windows 10 VM will be started by Parallels, based off the template it created. Ensure the Windows 10 VM image is properly shut down (not suspended).Edit the config.toml and add the SSH user and password under the section.Register a runner using Parallels as the executor.Create a Windows 10 Parallels VM and install/configure OpenSSH.Hard to know whether there's something intricate I am missing with Windows, or whether this might be a bug with Gitlab Runner itself. It appears as though GitLab Runner doesn't receive confirmation of this though and proceeds to do nothing which leads to the job timing out after a number of reattempts. The Runner receives the job and Parallels even creates the template VM and the linked image. Screenshot of error in the Runner pipeline However, the Windows 10 stages just hang endlessly and times out: The MacOS image works fine when a new build comes through, pipeline succeeds. When registering the runners I then proceeded to add the relevant SSH user and password details into the config.toml.

I'm using Parallels Executor in order to test/build/deploy an Electron+React application using a pre-prepared MacOS and Windows 10 VM which also have SSH access enabled (tested too). I originally posted an issue of what I believe to be a bug with GitLab Runner, but have sadly received no response on the GitLab-Runner repository.