mirror of
https://github.com/ovh/the-bastion.git
synced 2024-09-20 23:15:58 +08:00
c201f44d83
The chain of executions is as is:
- `docker_build_and_run_tests_all.sh`
- launches several instances of `docker_build_and_run_tests.sh`
- builds docker images with the `target_role.sh` and `tester_role.sh` entrypoints
- inside the tester docker, `tester_role.sh` launches `launch_tests_on_instance.sh`
- the target docker gets tested after setting up accounts, SSH etc.
Previously, these scripts passed options to each other either by a mix of environment
variables and command-line arguments, with some inconsistencies here and there.
Now, `launch_tests_on_instance.sh` supports a lot of command-line options, which can
be specified directly if testing a remote server, or can be passed-through by the calling
script in case of docker tests. `docker_build_and_run_tests.sh` and
`docker_build_and_run_tests_all.sh` also support to passthrough these options down.
22 lines
635 B
Bash
22 lines
635 B
Bash
# vim: set filetype=sh ts=4 sw=4 sts=4 et:
|
|
# shellcheck shell=bash
|
|
# shellcheck disable=SC2034
|
|
|
|
RED=$(printf "%b" '\033[31m')
|
|
GREEN=$(printf "%b" '\033[32m')
|
|
YELLOW=$(printf "%b" '\033[33m')
|
|
BLUE=$(printf "%b" '\033[34m')
|
|
MAGENTA=$(printf "%b" '\033[35m')
|
|
CYAN=$(printf "%b" '\033[36m')
|
|
LIGHTGRAY=$(printf "%b" '\033[37m')
|
|
DARKGRAY=$(printf "%b" '\033[90m')
|
|
|
|
BOLD_CYAN=$(printf "%b" '\033[1;36m')
|
|
|
|
WHITE_ON_RED=$(printf "%b" '\033[41m')
|
|
WHITE_ON_BLUE=$(printf "%b" '\033[44m')
|
|
BLACK_ON_GREEN=$(printf "%b" '\033[30m\033[42m')
|
|
BLACK_ON_RED=$(printf "%b" '\033[1;30m\033[41m')
|
|
|
|
NOC=$(printf "%b" '\033[0m')
|