2 commits

Author	SHA1	Message	Date
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
Thomas Haller	d719bab9f7	gitlab-ci: rename "build.sh" script to "run-test.sh" ... It's true, that our gitlab-ci test mostly consists of building NetworkManager. Hence the name of the script was not entirely wrong. But it's not only building. I think "run-test.sh" is a much better name. Rename.	2022-03-21 17:19:46 +01:00

Renamed from .gitlab-ci/build.sh (Browse further)