Hard to know whether there's something intricate I am missing with Windows, or whether this might be a bug with Gitlab Runner itself.Īny ideas? Really dont want to have to endure setting up another VM in VirtualBox runner just for Win10. 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. However, the Windows 10 stages just hang endlessly and times out: Microsoft has recently released a new emulator to bring support for 64-bit x86 programs for Windows 10 ARM. As shown in the photos, they know exactly how I am using it and approved the. The MacOS image works fine when a new build comes through, pipeline succeeds. I entered my Windows 10 activation key and it was fully embraced by Microsoft. When registering the runners I then proceeded to add the relevant SSH user and password details into the config.toml.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |