summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorTristan Van Berkom <tristan.vanberkom@codethink.co.uk>2017-07-14 18:23:45 +0900
committerJavier Jardón <jjardon@gnome.org>2017-07-25 23:17:42 +0100
commitf45e9f5aaea6842fd2322cbf4afdcf3ffd4f3223 (patch)
tree03f22f248aa107c94cf43ece11e5d28afdcd58fb /.gitlab-ci.yml
parent03ec21f5d3cb4139e169d083032a4140dbc6f693 (diff)
downloaddefinitions-f45e9f5aaea6842fd2322cbf4afdcf3ffd4f3223.tar.gz
.gitlab-ci.yml: Enable colors on the CI
BuildStream is unable to detect whether output has support for ANSI color codes automatically when running in a CI and not connected to a real tty. It is however typical of CI systems to support the ANSI color escape codes (but not other terminal escape sequences), for this reason BuildStream has an explicit --colors option to force colors to be enabled in scenarios where we cannot detect that it is supported. This patch causes the CI to use it.
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml4
1 files changed, 2 insertions, 2 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 2928f23b..a914fa7a 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -57,7 +57,7 @@ validate-all-definitions:
bst-build-system-x86_32-build:
stage: build-1
script:
- - bst -C buildstream-tests build build-system-x86_64-content.bst
+ - bst --colors -C buildstream-tests build build-system-x86_64-content.bst
dependencies:
- migrate-bst
@@ -121,7 +121,7 @@ gnome-build-64:
bst-gnome-build-64:
stage: build-3
script:
- - bst -C buildstream-tests build gnome/gnome-system-x86_64-content.bst
+ - bst --colors -C buildstream-tests build gnome/gnome-system-x86_64-content.bst
dependencies:
- migrate-bst