Thank you very much, but I don't know about the link ;)
My favourite piece is the remote testing capabilities. You can pitch test runs to either Windows/berrybrew and/or Unix/perlbrew installations, as long as you have Test::BrewBuild installed, and a tester running on them. You then go into your repository, and use the bbdispatch application to send out test runs (four run in parallel by default, which is configurable, and there is no limit to the number of remote test boxes to test on). This allows you to literally, with a single command, test against as many platforms and versions of Perl that you've got available:
Tester box 1 (Windows):
c:\> bbtester start
Tester box 2 (Unix) and dispatcher:
~/repos/mock-sub $ bbtester start
~/repos/mock-sub $ bbdispatch -t localhost -t 192.168.219.11
192.168.219.11 - MSWin32-x64-multi-thread
5.26.0_64 :: PASS
localhost - x86_64-linux
5.18.4 :: PASS
5.24.0 :: PASS
Using the -c aka --cmd command to bbdispatch and specifying a specific command string with the brewbuild command, you can also run against your revdeps on all remote testers:
~/repos/mock-sub $ bbdispatch -t localhost -t 192.168.219.11 -c 'brewb
+uild -R'
One more tidbit; You can set the system up to monitor a git repository, and automatically run your tests remotely every time the repository is updated. I use this functionality with a Raspberry Pi that has a 4 row by 20 col LCD screen that shows the status of testing, the commit etc, and also emails me on failure.
# -a, --auto
bbtester start -a
...
# -a, --auto
# -r, --repo (you don't need the https://github.com piece)
bbdispatch -t ... -r stevieb9/mock-sub -a
Of course, Git must be installed on all tester machines. By default, each tester keeps the fetched repos and test data in the brewbuild directory under your home directory (on both win and nix).
Happy New Year!
-stevieb | 