ovh/the-bastion
1
1
Fork 0
mirror of https://github.com/ovh/the-bastion.git synced 2025-01-06 15:31:56 +08:00
Code Issues Projects Releases Packages Wiki Activity
the-bastion/.github/workflows/freebsd.yml

34 lines
1.5 KiB
YAML
Raw Normal View History

feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
name: FreeBSD tests
on:
pull_request:
types: [labeled, synchronize]
jobs:
freebsd:
runs-on: macos-latest
name: FreeBSD
enh: tests: refactor the framework for more maintainability 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.
2021-06-08 00:38:16 +08:00
if: ${{ contains(github.event.pull_request.labels.*.name, 'tests:full') || contains(github.event.pull_request.labels.*.name, 'tests:long') || contains(github.event.pull_request.labels.*.name, 'tests:freebsd') }}
feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
steps:
- uses: actions/checkout@v2
- name: Functional tests under FreeBSD
chore: tests: always use the latest freebsd github action
2021-05-20 21:52:22 +08:00
uses: vmactions/freebsd-vm@main
feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
with:
usesh: true
chore: ghactions: use latest freebsdvm action version
2021-02-14 02:44:32 +08:00
sync: sshfs
feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
run: |
set -ex
freebsd-version
mount -o acls /
feat: httpproxy: add functional tests
2021-06-02 17:36:59 +08:00
pkg install -y bash rsync ca_root_nss jq fping screen flock curl
feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
mkdir -p /opt/bastion
rsync -a . /opt/bastion/
/opt/bastion/bin/admin/packages-check.sh -i
enh: freebsd: use ttyrec prebuild static version
2020-11-18 03:27:42 +08:00
/opt/bastion/bin/admin/install-ttyrec.sh -s
feat: add yubico-piv-checker install script
2020-12-30 17:56:41 +08:00
/opt/bastion/bin/admin/install-yubico-piv-checker.sh -s
enh: tests: refactor the framework for more maintainability 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.
2021-06-08 00:38:16 +08:00
/opt/bastion/bin/admin/install --new-install
feat: add FreeBSD automated tests
2020-11-17 19:47:41 +08:00
ssh-keygen -t ed25519 -f id_user
ssh-keygen -t ed25519 -f id_root
enh: tests: refactor the framework for more maintainability 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.
2021-06-08 00:38:16 +08:00
WANT_HTTP_PROXY=0 NO_SLEEP=1 user_pubkey=$(cat id_user.pub) root_pubkey=$(cat id_root.pub) TARGET_USER=user5000 /opt/bastion/tests/functional/docker/target_role.sh
/opt/bastion/tests/functional/launch_tests_on_instance.sh --module=500-http-proxy.sh --has-mfa=0 --has-mfa-password=1 --has-pamtester=1 --skip-consistency-check --remote-etc-bastion=/usr/local/etc/bastion 127.0.0.1 22 0 user5000 id_user id_root
Reference in a new issue Copy permalink