GitLab Runner connects to the virtual machine and executes a build.GitLab Runner creates a snapshot of the running virtual machine (this is done.GitLab Runner waits for the SSH server to become accessible.GitLab Runner starts or restores the snapshot of the virtual machine.The port-forwarding rules are created to access the SSH server.The virtual machine is cloned if it doesn’t exist.A unique name for the virtual machine is generated: runner-concurrent.
Enter the SSH user and password or path to identity_file of the.The settings of the virtual machine General > Basic > Name) Enter the name of the base virtual machine you created earlier (find it under.Register a new runner with gitlab-runner register.Install GitLab Runner on the host running VirtualBox.It’s completely fine to use automation tools like Vagrant to provision the Log out and shut down the virtual machine.If you want to upload job artifacts, install gitlab-runner inside the VM.Install all other dependencies required by your build.If Windows VM, see Checklist for Windows VMs.(optional) Configure another Network Adapter as “Bridged networking” to get access to the internet from the guest (for example).Configure Network Adapter 1 as “NAT” (that’s currently the only way the GitLab Runner is able to connect over SSH into the guest).Import or create a new virtual machine in VirtualBox.Otherwise, you will need to add the installation folder to the PATH environment variable of the gitlab-runner process. GitLab Runner will automatically detect it. If running from Windows and VirtualBox is installed at theĭefault location (for example %PROGRAMFILES%\Oracle\VirtualBox),.
To override the ~/builds directory, specify the builds_dir option under
0 kommentar(er)
