Investigating CI options for Samba test branches
abartlet at samba.org
Sun May 3 21:28:07 MDT 2015
Towards my proposal for faster release cycles, I've been looking into
how we can ensure developers use their own time better. In particular,
I'm really keen to see a situation where folks push 'try' branches to a
review server, and even if that isn't how the patch is finally merged,
that an autobuild 'just happens' against that tree.
That way, it is much less likely that the reviewer will have to re-push
things due to an autobuild failure, as if they look at the patch over 2
hours after it was written, the patch would have been automatically
So far, I've looked at the practical details of three systems.
- my cloud-autobuild scripts (on the Catalyst Cloud)
I've got a patch to support the latter two solutions attached and here
The cloud-autobuild scripts are at:
However, this solution requires an active step, pushing the build, and
of course an account on a cloud.
For drone.io, the build doesn't even start properly, perhaps there is a
disk space limit on their free plans. This is however an interesting
option, perhaps if we host it on our own (virtual) systems, as it meets
our requirement of being an open source project. I've asked for
increased limits on the hosted system, and am intrigued that if we
hosted it, it could apparently link back to a gitlab server.
For travis-ci.org, the build starts, but they have a hard limit after 50
mins, so the build also fails. It is also not open source.
Are there any other solutions we should be looking at, beyond just
running autobuld on sn-devel?
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
More information about the samba-technical