Hi,
On Mon, May 23, 2016 at 05:43:58PM +0200, Jens Neuhalfen wrote:
I'd prefer to keep the actual buildslave infrastructure private, with access
granted to only a select few. We already get email notifications to a public
list for each build failure.
Is there some kind of instruction to ?reproduce? the build infrastructure? Some
kind of document or - even better - something executable
(Vagrant/Docker/Salt/Puppet/..)?
https://community.openvpn.net/openvpn/wiki/SettingUpBuildslave
is what we currently have, but it only describes the slaves (talking to
Samuli's build master) - not sure if the master is documented anywhere.
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.
I would suggest extending Travis CI instead of trying to create a
private buildbot infrastructure. If *BSD is not supported by Travis,
then we obviously can't get rid of buildbot entirely anytime soon. Plus
we need the Windows "buildslave" (=custom scropt) for full cross-compile
tests and for publishing snapshot installers thus produced.
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).
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock