Hi,

On Sun, May 22, 2016 at 02:38:05PM +0200, Jens Neuhalfen wrote:
[???]

My buildbots test on "all the BSDs" (Free, Net, Open, and they have a
/bin/sh which is "It only supports features designated by POSIX plus a few
Berkeley extensions") and OpenSolaris 11 (ksh93).  Samuli's buildbot
test on various Linux variants, so "dash" should work.

Are these buildbots available vor the general public? Being able to easily test
lowers the bar for new contributors considerable.

Right now, not for "general public".  They auto-build (+test) every release
that gets commited to "master" - which, of course, means "it is too late
if it breaks platform <x>".

We have discussed building from test branches (on-demand), and widening the
access to these branches - but nothing specific has been decided yet.  Maybe
we should put that on the agenda for the monday meeting on May 30...

  - addition of new branches (at github), with more liberal commit rights
  - having the buildbots pull from github (right now they use sf, AFAIR)
  - opening the buildbot "build revision <x> on platform <y>" API for
    a wider circle (right now, I think only Samuli, David and I have access
    to that host, it's on private addresses in Samuli's VPN)

I'm a bit reluctant giving "full user account" access rights to developers
I have not met in person yet - but with the approach outlined above, at
least sanity checking "I think the patch is good, will it break one of the
more esoteric platforms?" will be possible.

Samuli, are you listening? ;-)

gert

Yes. I think a separate testing branch with more liberal commit rights combined with pulling from GitHub makes sense. I'm not sure what happens at the buildslaves if we decide rewind history - rewinding would be quite useful when working with pure testing branches in that we could make "testing" track master and whenever a bad patch is found, simply rewind back to the last known-good state.

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.

--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

Reply via email to