Breakpad requires continuous build infrastructure

[GoogleCodeExporter]

Breakpad currently has no continuous build infrastructure. This is a problem 
for various reasons:

- Developers have no easy way to validate if their change runs across all 
platforms, short of manually testing everywhere.
- The tree can be broken and nobody would know.
- There is no established process for building release binaries.

Original issue reported on code.google.com by chri...@chromium.org on 2 Apr 2014 at 1:11

[GoogleCodeExporter]

we were thinking of adding a buildbot to the Chromium OS waterfall to run 
breakpad tests.  did you guys have infra already in place you were thinking of 
using ?

Original comment by vapier@chromium.org on 2 Apr 2014 at 2:24

[GoogleCodeExporter]

This would be great, even just doing a build and running the existing unit 
tests would be fantastic. I've broken the build before and not noticed, and 
I've pulled down bad changes that would have been easily caught with CI.

Original comment by ted.mielczarek on 2 Apr 2014 at 3:27

[GoogleCodeExporter]

Yeah, I'm planning on adding a buildbot on Chrome's infrastructure. It'll be a 
'client' bot, so not on any of Chrome or ChromeOS's waterfalls, but a waterfall 
of its own, yet hosted on the same hardware. (I've done this previously for the 
Syzygy project.)

Original comment by chri...@chromium.org on 2 Apr 2014 at 4:21