Skip to content
Snippets Groups Projects
Verified Commit d0f016cf authored by Varac's avatar Varac
Browse files

Use stdbuf instead of unbuffer for CI timestamping

There are different reasons for this:

- Using `stdbuf` will correctly return and non-zero
  exit code so when something breaks during CI `gitlab-runner`
  will mark the build as failed (Resolves: #8821).
- `stdbuf` is already installed by the `coreutils` package and
  thus saves diskspace
parent 1078bfff
No related branches found
No related tags found
No related merge requests found
...@@ -60,7 +60,7 @@ deploy_test: ...@@ -60,7 +60,7 @@ deploy_test:
except: except:
- master - master
script: script:
- su -c '/usr/bin/unbuffer /bin/bash -o pipefail ./ci-build.sh | /usr/bin/ts' cirunner - su -c 'set -o pipefail; stdbuf -oL -eL ./ci-build.sh | ts' cirunner
# Latest job will only run on the master branch, which means all merge requests # Latest job will only run on the master branch, which means all merge requests
# that are created from branches don't get to deploy to the latest-ci server. # that are created from branches don't get to deploy to the latest-ci server.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment