bbdispatch - Dispatch Test::BrewBuild builds to remote test servers.


Dispatch a default brewbuild test run on the two listed remote servers, using the repository you're currently working in:

    bbdispatch -t -t

Dispatch a custom command to a single remote tester:

    bbdispatch -c "brewbuild -R" -t

Have the remote testers test a specified repository:

    bbdispatch -r -t

Run in automated continuous mode. Reruns all tests continuously in a loop:

    bbdispatch [...] -a

Automated continuous mode, but run only 10 runs:

    bbdispatch [...] -a 10

Add debugging to any other command string:

    bbdispatch [...] -d 0-7

Set maximum number of concurrent testers to communicate with (default is 4):

    bbdispatch [...] -f 8

Example output of a basic run where I'm in a git repository directory:

    bbdispatch -t localhost -t -t -t - x86_64-linux

    5.22.1 :: PASS - MSWin32-x64-multi-thread

    5.18.4 :: PASS
    5.22.1 :: PASS

    localhost - MSWin32-x64-multi-thread

    5.22.1 :: FAIL - amd64-freebsd

    5.22.1 :: PASS
    5.23.7 :: PASS
    5.8.9 :: FAIL
    5.10.1 :: FAIL
    5.18.4 :: FAIL

All FAIL log files are stored locally when dispatching to identify the issues. If I'm letting BrewBuild determine the repository, the files will be stored in ./bblog. If a repo is specified, they'll be put into ~/brewbuild/repo/bblog.


This script dispatches brewbuild build sets to pre-configured Test::BrewBuild::Tester test servers.

By default, we try to look up the repository information from your current working directory. If it can't be found, you must supply it on the command line or within the configuration file.


-t, --testers

A list of testers to dispatch to. Can be sent in multiple times. Format of the testers is IP:Port. If Port is ommitted, we'll default to 7800.

Testers can also be configured within the config file. Testers set on the CLI will override those.

-c, --cmd

By default, the testers will simply run brewbuild. You can send in any brewbuild commands here within quotes, so long as the first argument is brewbuild.

This option will override anything in the configuration file.

-r, --repo

By default, if a repository isn't specified in the config file, we'll attempt to locate the repository information from the current working directory.

The full path to the repo is necessary eg: If you are using Github, you can omit the URL portion as we'll automatically prepend if you simply send in user/repo-name.

Set this to the repo link to override both.

-d, --debug

Set to 0-7 to enable debug logging.

-f, --forks

By default, we maintain four (4) testers concurrently. Pass an integer to this argument to change the default number of concurrent testers.

-a, --auto

This command tells the dispatcher to throw tests at the Testers continuously. With no argument (or an argument of 0), we'll run forever. Any other integer will run in auto mode for that many cycles.

The --repo|-r parameter is *mandatory* when in auto mode.

-R, --rpi

This argument enables Raspberry Pi mode, and is *only* useful if running tests on an RPi, with an LCD connected, and bbdispatch is running in --auto mode. It requires the $ENV{BB_RPI_LCD} environment variable set, with a comma-separated list of pin numbers in the format '1,2,3,4,5,6', where the GPIO pin numbers are in the order of RS, E, D0, D1, D2, D3.

To use the larger 4 row by 20 column LCD, append the number of rows and columns to the end of the environment variable:



Steve Bertrand, <steveb at>


    perldoc brewbuild
    perldoc Test::BrewBuild

    perldoc bbtester
    perldoc Test::BrewBuild::Tester

    perldoc Test::BrewBuild::brewbuild.conf


Copyright 2017 Steve Bertrand.

This program is free software; you can redistribute it and/or modify it under the terms of either: the GNU General Public License as published by the Free Software Foundation; or the Artistic License.

See for more information.