[Buildbot-devel] Buildbot can do tests

[Vitali Lovich]

Huh.
That’s what we do.  We have 4 major tasks:

1. Tool deployment across the cluster; every day there’s a new batch from elsewhere in the company.  Far easier than traditional tools like chef since it has to always be up-to-date.
2. It receives a hook that tells it to checkout a git repository, read the configuration for the build from the git repository & then run those steps.  In other words, our buildmaster is a shim for executing the steps within a git repository which lets it scale to an arbitrary number of configurations, they’re automatically versioned so backwards/forwards compatibility isn’t an issue.
3. It has special knowledge of how to do automated posts to reviewboard & how to merge in a branch (update our bug tracker, merge feature into master correctly, run remaining steps, push merged result).
4. It has a generic post-merge task scheduler that again queries the git repository for the set of tasks to run in stages.

Aside from the tool deployment, it’s like the delivery pipeline plugin for Jenkins except built on buildbot.

-Vitali

> On Jun 19, 2015, at 11:05 AM, Tim Flink <tflink at redhat.com> wrote:
> 
> On Thu, 18 Jun 2015 09:58:45 +0000
> Pierre Tardy <tardyp at gmail.com <mailto:tardyp at gmail.com>> wrote:
> 
>> Hi,
>> 
>> I see a lot of misunderstanding about buildbot being a tool only
>> designed for doing builds and cannot run a testfarm. (
>> https://plus.google.com/+ThomasPetazzoni/posts/YUo9ohgboSJ)
>> 
>> Indeed, buildbot is initially created to do builds, and all the
>> glossary is around builds. We got buildsets that turn into
>> buildrequests that turn into builds, and set buildproperties.
>> 
>> Actually, buildbot is really a generic job scheduler, and is great at
>> managing slaves, and storing the logs of arbitrary jobs.
>> 
>> Some of my colleagues are working on building a TestFarm manager using
>> buildbot nine.
>> This is running great, and they are having very nice results, thanks
>> to the plugin design of the UI.
>> But one of the feedback of their users is that it is written 'build'
>> everywhere in the UI, while they are only controlling testfarm, using
>> builds that have been done in another buildbot master.
> 
> We're in a similar boat - we make heavy use of buildbot for what we're
> calling task automation (think test automation but far more generic -
> along the lines of job automation) for Fedora. Our system [1] has been
> in production [2] for about 9 months now - the load is somewhat low
> right now but I expect both the load and the complexity of the system to
> increase significantly after our next major release.
> 
> [1] http://fedoraproject.org/wiki/Taskotron <http://fedoraproject.org/wiki/Taskotron>
> [2] https://taskotron.fedoraproject.org/taskmaster/waterfall <https://taskotron.fedoraproject.org/taskmaster/waterfall>
> 
> I've been meaning to write up a more detailed explanation of how we're
> using buildbot and how it's becoming more critical for our ongoing
> automated test efforts in Fedora but until then, figured I could at
> least chime in to this thread :)
> 
> We've really made the "build" generic - it will clone a git repository
> based on how the build itself is triggered. After that clone, the task
> contained in the repo is executed and results are submitted to a
> central location. In the 99000+ "builds" that have been done in our
> production buildbot instance so far, I don't think that a single one
> would be considered a build in the traditional sense.
> 
> This is a bit impromptu but thanks for making such a flexible
> scheduling and execution framework available. It's helping us to
> increase the number of automated checks run on Fedora during
> development and enabling us to focus on the bits that are testing
> Fedora instead of spending all of our time writing a framework for
> scheduling and executing those tests/tasks.
> 
> Tim
> ------------------------------------------------------------------------------
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net <mailto:Buildbot-devel at lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel <https://lists.sourceforge.net/lists/listinfo/buildbot-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20150619/294e21e8/attachment.html>