The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.

NAME

App::Yath::Command::recent - Show a list of recent runs (using logs, database and/or web server)

DESCRIPTION

This command will find the last several runs from a yath server

USAGE

    $ yath [YATH OPTIONS] recent [COMMAND OPTIONS]

OPTIONS

Database Options

--db-config ARG
--db-config=ARG
--no-db-config

Module that implements 'MODULE->yath_db_config(%params)' which should return a App::Yath::Schema::Config instance.

Can also be set with the following environment variables: YATH_DB_CONFIG

--db-driver Pg
--db-driver MySQL
--db-driver SQLite
--db-driver MariaDB
--db-driver Percona
--db-driver PostgreSQL
--no-db-driver

DBI Driver to use

Can also be set with the following environment variables: YATH_DB_DRIVER

--db-dsn ARG
--db-dsn=ARG
--no-db-dsn

DSN to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_DSN

--db-host ARG
--db-host=ARG
--no-db-host

hostname to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_HOST

--db-name ARG
--db-name=ARG
--no-db-name

Name of the database to use

Can also be set with the following environment variables: YATH_DB_NAME

--db-pass ARG
--db-pass=ARG
--no-db-pass

Password to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_PASS

--db-port ARG
--db-port=ARG
--no-db-port

port to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_PORT

--db-socket ARG
--db-socket=ARG
--no-db-socket

socket to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_SOCKET

--db-user ARG
--db-user=ARG
--no-db-user

Username to use when connecting to the db

Can also be set with the following environment variables: YATH_DB_USER, USER

Harness Options

-d
--dummy
--no-dummy

Dummy run, do not actually execute anything

Can also be set with the following environment variables: T2_HARNESS_DUMMY

The following environment variables will be cleared after arguments are processed: T2_HARNESS_DUMMY

--procname-prefix ARG
--procname-prefix=ARG
--no-procname-prefix

Add a prefix to all proc names (as seen by ps).

The following environment variables will be set after arguments are processed: T2_HARNESS_PROC_PREFIX

Recent Options

--recent-max 10
--no-recent-max

Max number of recent runs to show

Web Client Options

--api-key ARG
--api-key=ARG
--no-api-key

Yath server API key. This is not necessary if your Yath server instance is set to single-user

Can also be set with the following environment variables: YATH_API_KEY

--grace
--no-grace

If yath cannot connect to a server it normally throws an error, use this to make it fail gracefully. You get a warning, but things keep going.

--request-retry
--request-retry=COUNT
--no-request-retry

How many times to try an operation before giving up

Note: Can be specified multiple times, counter bumps each time it is used.

--url http://my-yath-server.com/...
--uri http://my-yath-server.com/...
--no-url

Yath server url

Can also be set with the following environment variables: YATH_URL

Yath Options

--base-dir ARG
--base-dir=ARG
--no-base-dir

Root directory for the project being tested (usually where .yath.rc lives)

-D
-Dlib
-Dlib
-D=lib
-D"lib/*"
--dev-lib
--dev-lib=lib
--dev-lib="lib/*"
--no-dev-lib

This is what you use if you are developing yath or yath plugins to make sure the yath script finds the local code instead of the installed versions of the same code. You can provide an argument (-Dfoo) to provide a custom path, or you can just use -D without and arg to add lib, blib/lib and blib/arch.

Note: This option can cause yath to use exec() to reload itself with the correct libraries in place. Each occurence of this argument can cause an additional exec() call. Use --dev-libs-verbose BEFORE any -D calls to see the exec() calls.

Note: Can be specified multiple times

--dev-libs-verbose
--no-dev-libs-verbose

Be verbose and announce that yath will re-exec in order to have the correct includes (normally yath will just call exec() quietly)

-h
-h=Group
--help
--help=Group
--no-help

exit after showing help information

-p key=val
-p=key=val
-pkey=value
-p '{"json":"hash"}'
-p='{"json":"hash"}'
-p:{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
-p :{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
-p=:{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--plugin key=val
--plugin=key=val
--plugins key=val
--plugins=key=val
--plugin '{"json":"hash"}'
--plugin='{"json":"hash"}'
--plugins '{"json":"hash"}'
--plugins='{"json":"hash"}'
--plugin :{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--plugin=:{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--plugins :{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--plugins=:{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--no-plugins

Load a yath plugin.

Note: Can be specified multiple times

--project ARG
--project=ARG
--project-name ARG
--project-name=ARG
--no-project

This lets you provide a label for your current project/codebase. This is best used in a .yath.rc file.

--scan-options key=val
--scan-options=key=val
--scan-options '{"json":"hash"}'
--scan-options='{"json":"hash"}'
--scan-options(?^:^--(no-)?(?^:scan-(.+))$)
--scan-options :{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--scan-options=:{ KEY1 VAL KEY2 :{ VAL1 VAL2 ... }: ... }:
--no-scan-options
/^--(no-)?scan-(.+)$/

Yath will normally scan plugins for options. Some commands scan other libraries (finders, resources, renderers, etc) for options. You can use this to disable all scanning, or selectively disable/enable some scanning.

Note: This is parsed early in the argument processing sequence, before options that may be earlier in your argument list.

Note: Can be specified multiple times

--show-opts
--show-opts=group
--no-show-opts

Exit after showing what yath thinks your options mean

--user ARG
--user=ARG
--no-user

Username to associate with logs, database entries, and yath servers.

Can also be set with the following environment variables: YATH_USER, USER

-V
--version
--no-version

Exit after showing a helpful usage message

SOURCE

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/.

MAINTAINERS

Chad Granum <exodist@cpan.org>

AUTHORS

Chad Granum <exodist@cpan.org>

COPYRIGHT

Copyright Chad Granum <exodist7@gmail.com>.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

See http://dev.perl.org/licenses/