Thomas Haller bbd053bf83 gitlab-ci: print environment variables not part of run-test.sh script ... The output of our test scripts is captured by gitlab. It does however sanitize things that look like secrets. So it was reasonably save to call `env` from within the test script. Next, we will redirect (`tee`) the output of the test script to a file and archive it. When we do that, the output does not get sanitized and can be downloaded from the artifacts page. Stop running `env` as part of the test script. Do it instead as a separate step. After all, it is useful to see the environment variables of the test. But sanitized.		2022-03-21 17:19:47 +01:00
..
alpine-install.sh	gitlab-ci: enable test build on alpine linux	2020-12-11 18:14:10 +01:00
ci.template	gitlab-ci: print environment variables not part of run-test.sh script	2022-03-21 17:19:47 +01:00
config.yml	gitlab-ci: bump tag to regenerate containers	2022-03-16 00:58:41 +01:00
debian-install.sh	gitlab-ci: make "contrib/debian/REQUIRED_PACKAGES" verbose during container installation	2022-03-16 21:40:54 +01:00
fedora-install.sh	gitlab-ci: fix CentOS Linux 8 containers during ".gitlab-ci/fedora-install.sh"	2022-02-21 17:03:36 +01:00
run-test.sh	gitlab-ci: print environment variables not part of run-test.sh script	2022-03-21 17:19:47 +01:00