Investigating CI options for Samba test branches

[ronnie sahlberg]

I kind of like buildbot, eventhough it is one of the older and from UI
perspective uglier ones.
But it is easy to work with.

You can specify that it will monitor for multiple branches, so for
example I monitor for both master and the buildbot branch:

...
c['change_source'].append(GitPoller(
        'https://github.com/sahlberg/libnfs',
        workdir='gitpoller-workdir', branches=['master', 'buildbot'],
pollinterval=60))
...

I also have it only build 'buildbot' changes on a single machine but I
build changes to master on all machines in the farm:
...
c['schedulers'].append(SingleBranchScheduler(
                            name="all",
                            change_filter=filter.ChangeFilter(branch='master'),
                            treeStableTimer=None,
                            builderNames=["mint17",
                                          "fedora18",
                                          "opensuse12",
                                          "raspberrypi",
                                          "solaris11",
                                          "freebsd-9.3",
...

c['schedulers'].append(SingleBranchScheduler(
                            name="mint17",
                            change_filter=filter.ChangeFilter(branch='buildbot'\
),
                            treeStableTimer=None,
                            builderNames=["mint17"]))
...


Not he best or greatest by any stretch, but it works.
I just have to    git push --force origin buildbot:buildbot
when I want the buildbot to test my branch.

You probably want one buildbot branch and scheduler for each person.



On Tue, May 5, 2015 at 6:06 PM, Andrew Bartlett <abartlet at samba.org> wrote:
> On Tue, 2015-05-05 at 09:58 +0200, Ralph Böhme wrote:
>> On Tue, May 05, 2015 at 01:34:14PM +1200, Andrew Bartlett wrote:
>> > On Mon, 2015-05-04 at 07:06 +0200, Ralph Böhme wrote:
>> > > On Mon, May 04, 2015 at 03:28:07PM +1200, Andrew Bartlett wrote:
>> > > > Are there any other solutions we should be looking at, beyond just
>> > > > running autobuld on sn-devel?
>> > >
>> > > selfhosted buildbot.net ?
>> >
>> > Thanks, that also looks like another good option.
>> >
>> > In parallel, I've asked nicely, and travis-ci.org is extending my build
>> > time so I can run our full autobuild.
>> >
>> > The main blocker that I see to any of this is either
>> >  - using github (a number of us are uncomfortable about hitching our
>> > project to non-free network services like that, both for free software
>> > and project longivity reasons)
>> >  - for the open source options (buildbot.net, drone.io), having a gitlab
>> > or similar instance for such a tool to report back to.
>>
>> Not sure I understand why buildbot should require something like
>> gitlab for reporting. It has a simple web UI and can of course report
>> via email.
>
> I've looked at some buildbot instances, but I can't see how you would
> follow an ad-hoc try branch there.  The key for me is that it reports
> into a tool that can also be used for review, and that the link to
> getting and perhaps reviewing the code (ie to gitlab) includes the build
> status.
>
> Andrew Bartlett
>
> --
> Andrew Bartlett
> http://samba.org/~abartlet/
> Authentication Developer, Samba Team  http://samba.org
> Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba
>
>
>
>