...
The buildmaster part is not documented anywhere. I have shared the master
config once when someone requested it - there is nothing inherently private in
there, once the passwords are removed. Setting up buildmaster + buildslaves
could definitely be automated, but it would be a rather massive task.
Samuli, could you send me the scripts? I’d like to have a look. Maybe there is
something that can be replicated. This is something I’d try to add to the
scripted integration tests (Vagrant) already in the pipeline.
I published the Windows "buildslave" script here, along with some basic
documentation:
<https://github.com/mattock/openvpn-windows-buildtest>
I also cleaned up the buildmaster configuration and will publish it
later. However, there will be several hacks in there to accommodate
quirks in our current buildslaves (e.g. NetBSD), so making it fully
generic would require some refactoring.
Could we use Travis CI with a huge combination of operating systems and build
flags? Or does this kind of use go outside its scope? Right now each commit
triggers something like 150 builds on the buildslaves (in total).
From what I know, this is not possible. 150 build? Whoah, thats quite a few.
I’d expect 2-3 per supported OS. Is this a case of combinatoric explosion?
Yeah. we trigger at least 16 builds per buildslave/OS, can't check the
exact number right now. This is because of the large number of configure
flags we need to support.
It seems that basic smoke testing with Travis CI before pushing anything
to the repository makes sense, but it's not a full buildbot replacement.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
