This is an archive of the discontinued LLVM Phabricator instance.

Start Docker-izing sanitizer-windows
ClosedPublic

Authored by rnk on Dec 15 2020, 2:42 PM.

Details

Summary

This defines a new docker image for sanitizer-windows based on the
existing docker image. I chose to dockerize sanitizer-windows first,
because it cycles quickly and doesn't do a two-stage build.

My plan is to have both the existing sanitizer-windows bot and the new
one run concurrently, but the new one will connect to the silent,
staging buildmaster (lab.llvm.org:9994). Once we are ready to cut over,
I will turn off the old sanitizer-windows VM and update this port in the
docker image and redeploy.

I am chosing to stick with the buildbot annotation script approach,
because it allows for much faster iteration: I can adjust paths for the
VS installation for example simply by committing to zorg. However, both
the live and staging bot will use the same script, so the same script
must work for both sanitizer-windows bots at the same time!

Diff Detail

Event Timeline

rnk requested review of this revision.Dec 15 2020, 2:42 PM
rnk created this revision.
kuhnel accepted this revision.Dec 16 2020, 1:58 AM

LGTM.

I'm not using the current deployment of the "windows10_vs2019" any more. So feel free to just modify that image and re-use the worker-config. That way you don't have to configure another deployment.

If you don't want to use that, I'll just delete to save resources.

buildbot/google/docker/buildbot-sanitizer-windows/Dockerfile
3

This base image still contains GnuWin, Python2 and an ancient version of the buildbot-worker.
So when starting with a new worker I guess we should clean that up (remove python2 and GnuWin, and upgrade to the latest builbot-worker)

This revision is now accepted and ready to land.Dec 16 2020, 1:58 AM
This revision was automatically updated to reflect the committed changes.