RBULK-REPORT(1)

NAME
rbulk-report - collect log files from robotpkg bulk builds

SYNOPSIS
rbulk-report log2db [-path category] dir sqlite.db
rbulk-report db2html sqlite.db destdir
rbulk-report rm sqlite.db pkg
rbulk-report rmarch sqlite.db arch

DESCRIPTION
rbulk-report collect various log files generated from a robotpkg bulk build session and creates a pretty HTML summary.

rbulk-report can be invoked in differents ways. The first argument is a command that specifies the action to take. Valid commands are:

log2db [-path category]
    dir sqlite.db Reads a complete session log, as created by rbulk-build(1). dir is expected to contain a general <arch>.log file, named after the architecture name. dir should also contain one directory entry for each package that was built. If the -path option is given, only packages whose PKGPATH match category are taken into account. The results are stored in the sqlite database sqlite.db and all log files are deleted.

db2html sqlite.db destdir
    Generates a complete, static HTML report in destdir from the sqlite.db database contents.

rm sqlite.db pkg
    Deletes all occurences of the package pkg in the sqlite.db database. pkg must refer to the complete package name (including version and options) and not just the package base.

rmarch sqlite.db arch
    Deletes all package entries associated with the architecture arch in the sqlite.db database.

NOTES
rbulk-report is not very generic and probably not useful at all if you are not doing bulk builds of robotpkg with rbulk-build(1).

SEE ALSO
rbulk-build(1).