Autotesting dub packages with dmd nightly

[qznc via Digitalmars-d-announce]

On Saturday, 16 July 2016 at 20:34:49 UTC, Sebastiaan Koppe wrote:
> Just to let you guys know - and to be sure no one is doing the 
> same - I decided to go ahead and *start* writing an autotester 
> that will fetch dmd nightly and unittest each dub package.
>
> It will be using a classic master-worker architecture and will 
> leverage docker containers.
>
> I am aiming really low at first, but will eventually add things 
> like memory usage, history, notifications, etc.

Great! Maybe I can help you? Do you have a repository somewhere 
already?

I don't think nightlies are that important. Older releases, 
alpha/beta versions, LDC, and GDC seem more important for me. For 
example, I would like to know if a dub package which was last 
updated two years ago is still working with the current dmd.

The hardest part is probably the work distribution. It should 
work across platforms, so we can (eventually) test Windows, 
Android, Raspberry Pi, etc.

I don't believe GitLab would be a good idea. It is not built for 
this and I find the CI parts quite minimal. I have some buildbot 
experience, it would fit, but is a bitch to maintain. Maybe v0.9 
is better when it is finished, but development happened at 
glacial speed in the last years (!).

If we build something custom, the question is: Dogfooding or not? 
With (e.g.) Python we would have something working much quicker.