Running a Windows buildbot differs from Linux a bit. So this document will give hints on the differences.
To create a new Dockerfile and you do not have a local Windows machine, create a VM in the the cloud.
For frequent access to your Windows VM it's conveneint to install Remmina, a remote desktop client for Linux, to connect the the Windows VM.
choco install -y git vscode googlechrome arcanist vim
ssh-keygen, upload your public key to Github.
git clone ssh://email@example.com/llvm/llvm-zorg.git
Install-PackageProvider -Name NuGet -Force Install-Module -Name DockerMsftProvider -Repository PSGallery -Force Install-Package -Name docker -ProviderName DockerMsftProvider -Force sc.exe config docker start=delayed-autoThen reboot your VM to start the Docker service.
gcloud auth loginand
gcloud auth configure-dockerto be able to push images to the registry.
tokensomewhere and store your worker password there. You will need this to test your worker locally.
Premerge-testing is also running LLVM builds on Windows. You might be able to get some ideas from there.
Git on Windows includes a bash. Right-click the Start menu und launch a “Windows Powershell (Admin)” (with admin rights, as docker requires that) and run
bash from there. Then you should be able to use the helper scripts (e.g.
build_run.sh) on Windows as well.
If Windows seems stuck, use the
Resource Monitor to check what the processes are doing. If you need even more insight, e.g. debugging builds or test, use the
Process Explorer (
choco install procexp) to figure out what's going on.
windows-base-vscode2019 image, it contains everything you need to build and test with Visual Studio 2019.