/ 
Test-BrewBuild-2.06
River stage zero No dependents
/ Test::BrewBuild::Tutorial

NAME

Test::BrewBuild::Tutorial - Basic overview of using the client/server aspects of the Test::BrewBuild build system

DESCRIPTION

This document gives a basic overview of setting up remote test servers, and how to dispatch build requests to them.

BEFORE YOU BEGIN

At this time, there is no security around the network portions of this suite. To mitigate, you can use IP filters, SSH tunnels etc. We do however do a reasonably good job of ensuring the commands executed on the testers have been verified.

Read through the brewbuild documentation so you know how the actual tester works. Documentation for the scripts used in this tutorial can be found in "SEE ALSO".

You'll need Git on both the dispatcher and all testers, your module accessible via a Git repository, and the dispatch and all tester servers configured, see "SERVER CONFIGURATION".

SERVER CONFIGURATION

Recommended initial platform configuration guide: Test Platform Configuration.

This applies to all Test::BrewBuild systems, whether they'll be stand-alone, a dispatcher or a tester.

SCENARIO

You've got a Linux box at 10.1.1.1 with all IP addresses and ports bound on the server available for listening on.

You've also got a Windows server on 172.16.1.1, but our default port TCP 7800 is not available, which can only listen on that specific IP address.

You will be dispatching from a FreeBSD server, so you also want to run a tester on the localhost.

On the dispatcher, we'll be located within a Git repository directory, so we'll let the system take care of the repo management so we don't have to continuously specify it.

See "SEE ALSO" for more elaborate uses, command-line options of each script, and details of the optional configuration file.

STEP 1: CONFIGURE TESTERS

Linux (10.1.1.1)

Since we can listen on all IPs and the default port is available for use, this simple command will start the tester, and put it into the background:

bbtester start

Windows (172.16.1.1)

On this server, we're not permitted to listen on all IP addresses, and since port 7800 is unavailable, we have to specify an alternate.

bbtester start -i 172.16.1.1 -p 9999

localhost

Since this tester is the dispatching server, we don't want it listening on public-facing IP addresses, so we'll specify just the local loopback:

bbtester start -i 127.0.0.1

STEP 2: CONFIGURE DISPATCHER

COMMAND LINE BASIC RUN

brewbuild itself can send in test run to remotes in an extremely basic way, but we're going to focus on bbdispatch here which allows for far more complex cases.

By default, we dispatch the most basic build, by sending brewbuild as the test command. The following will dispatch a build to all three testers we configured above, and then wait for them to return the results.

bbdispatch -t 127.0.0.1 -t 172.16.1.1:9999 -t 10.1.1.1

To specify a different command string:

bbdispatch -c "brewbuild -r -R -d 7" -t 127.0.0.1 -t 172.16.1.1:9999 -t 10.1.1.1

To specify a different repository:

bbdispatch -r https://github.com/user/repo -t 127.0.0.1 -t 172.16.1.1:9999 -t 10.1.1.1

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

bbdispatch -t localhost -t 192.168.252.90 -t 192.168.252.96 -t 192.168.252.95

192.168.252.95 - x86_64-linux

5.22.1 :: PASS

192.168.252.90 - MSWin32-x64-multi-thread

5.18.4 :: PASS
5.22.1 :: PASS

localhost - MSWin32-x64-multi-thread

5.22.1 :: FAIL

192.168.252.96 - 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:

192.168.252.96_5.10.1-FAIL.bblog
192.168.252.96_5.18.4-FAIL.bblog
192.168.252.96_5.8.9-FAIL.bblog
localhost_5.22.1-FAIL.bblog

CONFIGURATION FILE RUN

In your configuration file, you can set up all of your testers, along with the preferred command string (and repository if need be):

[dispatch]
cmd = brewbuild -R -d 7
testers = 127.0.0.1, 172.16.1.1:9999, 10.1.1.1

Then your dispatch run can be initiated simply by:

bbdispatch

TROUBLESHOOTING

If your dispatcher doesn't seem to be doing the right thing, you can enable debug logging, which will print directly to STDOUT:

bbdispatch [...] -d 7

If your testers don't seem to be behaving properly, first, log into the remote server and stop the currently running tester:

bbtester stop

Restarting the tester in daemon mode with a debug level will include its logging in the return to the dispatcher:

bbtester start -d 7

You can also run the tester in the foreground, and get its logging displayed to STDOUT live-time:

bbtester --fg -d 7 --stdout

If you want to get the debugging information from the actual brewbuild process included in the tester debug results, call brewbuild from the dispatcher with debug flags enabled. These debug results will be either included in the tester's return, or printed to its STDOUT, depending on how you're debugging the tester:

bbdispatch [...] -c "brewbuild -d 7"

Using the Test::BrewBuild::Dispatch API, you can enclose all debug output and return values into one scalar variable, and either dump it to a file or examine it all in one location:

use Capture::Tiny qw(capture_stdout);
use Test::BrewBuild::Dispatch;
use Test::BrewBuild::Tester;

my $return;

my $stdout = capture_stdout {
    my $d = Test::BrewBuild::Dispatch->new(debug => 7);
    my $t = Test::BrewBuild::Tester->new(debug => 7);

    $t->start;

    $return = $d->dispatch(
        cmd     => 'brewbuild -i 5.10.1_32 -d 7',
        repo    => 'https://stevieb9@github.com/stevieb9/mock-sub',
        testers => [ qw(10.1.1.1) ],
    );

    $t->stop;
};

$return .= $stdout;

print $return;

QUICK START

Quick start basic example, with one remote tester.

Tester 10.1.1.1:

bbtester start

brewbuild:

brewbuild -D -t 10.1.1.1

Dispatcher:

bbdispatch -t 10.1.1.1

SEE ALSO

Details on the configuration file.

Dispatch script usage information: bbdispatch.

Tester script usage information: bbtester.

BrewBuild script usage information: brewbuild.